From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Brian Foster <bfoster@redhat.com>,
fstests@vger.kernel.org, linux-bcachefs@vger.kernel.org,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] safe_macros: Fix bcachefs failure old kernel
Date: Wed, 17 Jan 2024 21:53:48 +0100 [thread overview]
Message-ID: <20240117205348.GB2723246@pevik> (raw)
In-Reply-To: <Zaf53YElGwHq04Sl@yuki>
> Hi!
> > I'm sorry, although man bcachefs(8) mentions fusemount, I haven't
> > figured out how to mount filesystem. Am I missing something?
> > Also, maybe for the start I would prefer to to test just kernel
> > functionality (no fuse).
> So this means that mount.bcasefs does exist, but the mount() fails? That
> sounds like something wasn't wired up properly.
Yes, mount.bcasefs exists, at least on openSUSE Tumbleweed (I suppose elsewhere
as well). Everything is done by single binary bcachefs.
ls -la /sbin/* |grep bcachefs
-rwxr-xr-x 1 root root 1424080 Jan 9 15:00 /sbin/bcachefs
lrwxrwxrwx 1 root root 8 Jan 9 15:00 /sbin/fsck.bcachefs -> bcachefs
lrwxrwxrwx 1 root root 8 Jan 9 15:00 /sbin/fsck.fuse.bcachefs -> bcachefs
lrwxrwxrwx 1 root root 8 Jan 9 15:00 /sbin/mkfs.bcachefs -> bcachefs
lrwxrwxrwx 1 root root 8 Jan 9 15:00 /sbin/mkfs.fuse.bcachefs -> bcachefs
lrwxrwxrwx 1 root root 8 Jan 9 15:00 /sbin/mount.bcachefs -> bcachefs
lrwxrwxrwx 1 root root 8 Jan 9 15:00 /sbin/mount.fuse.bcachefs -> bcachefs
> > Kind regards,
> > Petr
> > lib/tst_supported_fs_types.c | 5 +++++
> > 1 file changed, 5 insertions(+)
> > diff --git a/lib/tst_supported_fs_types.c b/lib/tst_supported_fs_types.c
> > index 369836717..21765c370 100644
> > --- a/lib/tst_supported_fs_types.c
> > +++ b/lib/tst_supported_fs_types.c
> > @@ -96,6 +96,11 @@ static enum tst_fs_impl has_kernel_support(const char *fs_type)
> > SAFE_RMDIR(template);
> > + if (!strcmp(fs_type, "bcachefs") && tst_kvercmp(6, 7, 0) < 0) {
> > + tst_res(TINFO, "bcachefs skipped on kernel < 6.7");
> > + return TST_FS_UNSUPPORTED;
> > + }
> I would rather turn this into a FUSE specific blacklist without a kernel
> version, since bcachefs got into the kernel I do not think the fuse
> version would be useful for testhing at all, so what about:
Your code makes sense, I'll test it.
Kind regards,
Petr
> diff --git a/lib/tst_supported_fs_types.c b/lib/tst_supported_fs_types.c
> index 369836717..4110c826e 100644
> --- a/lib/tst_supported_fs_types.c
> +++ b/lib/tst_supported_fs_types.c
> @@ -33,6 +33,11 @@ static const char *const fs_type_whitelist[] = {
> NULL
> };
> +static const cahr *const fs_type_fuse_blacklist[] = {
> + "bcachefs",
> + NULL,
> +};
> +
> static const char *fs_types[ARRAY_SIZE(fs_type_whitelist)];
> static int has_mkfs(const char *fs_type)
> @@ -96,6 +101,11 @@ static enum tst_fs_impl has_kernel_support(const char *fs_type)
> SAFE_RMDIR(template);
> + if (tst_fs_in_skiplist(fs_type, tst_fs_type_fuse_blacklist)) {
> + tst_res("Skipping %s because of FUSE blacklist", fs_type);
> + return TST_FS_UNSUPPORTED;
> + }
> +
> /* Is FUSE supported by kernel? */
> if (fuse_supported == -1) {
> ret = open("/dev/fuse", O_RDWR);
> > /* Is FUSE supported by kernel? */
> > if (fuse_supported == -1) {
> > ret = open("/dev/fuse", O_RDWR);
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-01-17 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 15:05 [LTP] [PATCH 1/1] safe_macros: Fix bcachefs failure old kernel Petr Vorel
2024-01-11 15:13 ` pvorel
2024-01-17 16:01 ` Cyril Hrubis
2024-01-17 20:53 ` Petr Vorel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240117205348.GB2723246@pevik \
--to=pvorel@suse.cz \
--cc=bfoster@redhat.com \
--cc=chrubis@suse.cz \
--cc=fstests@vger.kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox