public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: pvorel <pvorel@suse.de>
To: Cyril Hrubis <chrubis@suse.cz>, Li Wang <liwang@redhat.com>,
	Jan Stancek <jstancek@redhat.com>,
	Xiao Yang <yangx.jy@fujitsu.com>,
	Yang Xu <xuyang2018.jy@fujitsu.com>
Cc: ltp@lists.linux.it, Kent Overstreet <kent.overstreet@linux.dev>,
	Brian Foster <bfoster@redhat.com>,
	linux-bcachefs@vger.kernel.org, fstests@vger.kernel.org,
	Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>
Subject: ENODEV on bcachefs on kernel < 6.7 [was: Re: [PATCH v2 0/3] Add support bcachefs filesystem]
Date: Thu, 11 Jan 2024 15:05:36 +0100	[thread overview]
Message-ID: <067cf38108dd5b088168628d569f79c1@suse.de> (raw)
In-Reply-To: <ZZvK9OL6MduUpWZQ@yuki>

Hi all,

I'm sorry I haven't tested LTP with bcachefs-tools and kernel < 6.7. 
Quite a lot of tests fails:

# LTP_SINGLE_FS_TYPE=bcachefs ./chdir01
tst_buffers.c:56: TINFO: Test is using guarded buffers
tst_device.c:96: TINFO: Found free device 0 '/dev/loop0'
tst_test.c:1709: TINFO: LTP version: 20230929-269-g958402a95
tst_test.c:1593: TINFO: Timeout per run is 0h 00m 30s
tst_supported_fs_types.c:151: TINFO: WARNING: testing only bcachefs
tst_supported_fs_types.c:122: TINFO: FUSE does support bcachefs
tst_supported_fs_types.c:57: TINFO: mkfs.bcachefs does exist
tst_test.c:1669: TINFO: === Testing on bcachefs ===
tst_test.c:1117: TINFO: Formatting /dev/loop0 with bcachefs opts='' 
extra opts=''
tst_test.c:1131: TINFO: Mounting /dev/loop0 to 
/tmp/LTP_chdwqhGtZ/mntpoint fstyp=bcachefs flags=0
tst_test.c:1131: TBROK: mount(/dev/loop0, mntpoint, bcachefs, 0, (nil)) 
failed: ENODEV (19)

Library fails on safe_mount(). I wonder if we should check for kernel >= 
6.7 in case of bcachefs, or if we should return 0 in safe_mount() in 
case of bcachefs and errno == ENODEV (and possibly kernel < 6.7).

Kind regards,
Petr

      parent reply	other threads:[~2024-01-11 14:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 19:40 [PATCH v2 0/3] Add support bcachefs filesystem Petr Vorel
2023-12-07 19:40 ` [PATCH v2 1/3] lib: Add Bcachefs magic Petr Vorel
2024-01-12 13:18   ` Su Yue
2024-01-12 13:58     ` Petr Vorel
2023-12-07 19:40 ` [PATCH v2 2/3] lib: Add support bcachefs filesystem to .all_filesystems Petr Vorel
2023-12-07 19:40 ` [PATCH v2 3/3] statx04: Skip STATX_ATTR_COMPRESSED on Bcachefs Petr Vorel
2023-12-13  2:46   ` Kent Overstreet
2024-01-08 10:01     ` Cyril Hrubis
2024-01-08 20:54       ` Kent Overstreet
2024-01-09 10:32         ` Cyril Hrubis
2024-04-19 13:11           ` [LTP] " Cyril Hrubis
2024-05-07  8:18             ` Petr Vorel
2024-05-07 14:16               ` Kent Overstreet
2024-05-07 17:03                 ` Petr Vorel
2023-12-12 14:48 ` [PATCH v2 0/3] Add support bcachefs filesystem Jan Kara
2023-12-13 16:51   ` Jan Kara
2024-01-08 10:14 ` Cyril Hrubis
2024-01-08 20:04   ` Petr Vorel
2024-01-11 14:05   ` pvorel [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=067cf38108dd5b088168628d569f79c1@suse.de \
    --to=pvorel@suse.de \
    --cc=amir73il@gmail.com \
    --cc=bfoster@redhat.com \
    --cc=chrubis@suse.cz \
    --cc=fstests@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=jstancek@redhat.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=xuyang2018.jy@fujitsu.com \
    --cc=yangx.jy@fujitsu.com \
    /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