Re: [PATCH v2 2/4] common/xfs: helper function to check if -l/-d/-r concurrecy flags.
Zorro Lang <[email protected]>
| Newsgroups | org.kernel.vger.fstests,org.kernel.vger.linux-xfs |
|---|---|
| Message-ID | <agdC-BpP076q-RWb@zlang-mailbox> |
On Thu, May 14, 2026 at 01:39:11PM +0200, Lukas Herbolt wrote: > Check if the requested flag is supported by the mkfs.xfs on scratch > device. > > Signed-off-by: Lukas Herbolt <[email protected]> > --- > --- > changes v2: > -l/-d were introduced at same release no need to check both > common/xfs | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/common/xfs b/common/xfs > index f7a6d2f2f03a..c48b043faf80 100644 > --- a/common/xfs > +++ b/common/xfs > @@ -2399,3 +2399,12 @@ _require_xfs_healer() > _xfs_healer --supported "$@" &>/dev/null || \ > _notrun "health monitoring not supported on this kernel" > } > + > +# -l/-d concurrency came in same xfsprogs release v6.7 > + _scratch_mkfs_xfs_supports_concurrency() > +{ > + local arg="${1:-d}" > + > + test "$arg" = "-l" && arg="-d" > + _scratch_mkfs_xfs_supported "$arg" concurrency=0 Fair enough. It seems this 'compromise' is a workaround to avoid passing a log device to _scratch_mkfs_xfs_supported. Reviewed-by: Zorro Lang <[email protected]> > +} > -- > 2.54.0 >