From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Christoph Hellwig <hch@infradead.org>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: generic/730: exclude btrfs for now
Date: Wed, 4 Jun 2025 06:24:24 -0700 [thread overview]
Message-ID: <aEBJCG1_VRDggo6N@infradead.org> (raw)
In-Reply-To: <76226c51-78c5-4113-a04d-694a50b98557@gmx.com>
On Wed, Jun 04, 2025 at 06:47:41PM +0930, Qu Wenruo wrote:
> Right, the ext4/xfs can go a superblock shutdown because they are single
> device fs (except the external journal device),
XFS also has a RT device in addition to that.
> and fs_holder_ops handles
> the single device failure by calling back into the super block shutdown call
> back.
>
> For a multi-device fs, it should go through the blk_holder_ops, which btrfs
> doesn't provide when opening the devices.
Yes, btrfs would need it's own fs_ops. Alternatively we could add a new
->devloss super_operations method and change fs_bdev_mark_dead to
something like:
if (sb->s_op->devloss && sb->s_op->devloss(sb, bdev, surprise))
goto done;
<sync fs and stuff)
if (sb->s_op->shutdown)
sb->s_op->shutdown(sb);
done:
super_unlock_shared(sb);
so that btrfs or other multi-device file systems don't have to duplicate
the logic.
> I guess it means, if a fs supports per-bdev shutdown, it won't hurt to also
> provide a full-fs shutdown ioctl?
Supporting it is a good idea in general as it enables a lot of good test
coverage in xfstests.
next prev parent reply other threads:[~2025-06-04 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 6:25 [PATCH] fstests: generic/730: exclude btrfs for now Qu Wenruo
2025-06-04 8:25 ` Christoph Hellwig
2025-06-04 9:17 ` Qu Wenruo
2025-06-04 13:24 ` Christoph Hellwig [this message]
2025-06-06 10:55 ` Qu Wenruo
2025-06-05 13:55 ` Zorro Lang
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=aEBJCG1_VRDggo6N@infradead.org \
--to=hch@infradead.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.