linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Christian Brauner <brauner@kernel.org>
Cc: ntfs3@lists.linux.dev, jack@suse.cz,
	"Darrick J. Wong" <djwong@kernel.org>,
	Dave Chinner <david@fromorbit.com>,
	Qu Wenruo <quwenruo.btrfs@gmx.com>,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-xfs@vger.kernel.org, Qu Wenruo <wqu@suse.com>,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-btrfs@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [f2fs-dev] [PATCH v4 1/6] fs: enhance and rename shutdown() callback to remove_bdev()
Date: Thu, 10 Jul 2025 03:54:09 -0700	[thread overview]
Message-ID: <aG-b0UiIEX4G2-UC@infradead.org> (raw)
In-Reply-To: <20250708-geahndet-rohmaterial-0419fd6a76b3@brauner>

On Tue, Jul 08, 2025 at 09:55:14AM +0200, Christian Brauner wrote:
> I think letting filesystems implement their own holder ops should be
> avoided if we can. Christoph may chime in here.

Ccing helps for that..

>
> I have no appettite for
> exporting stuff like get_bdev_super() unless absolutely necessary. We
> tried to move all that handling into the VFS to eliminate a slew of
> deadlocks we detected and fixed. I have no appetite to repeat that
> cycle.

Exactly.

> The shutdown method is implemented only by block-based filesystems and
> arguably shutdown was always a misnomer because it assumed that the
> filesystem needs to actually shut down when it is called. IOW, we made
> it so that it is a call to action but that doesn't have to be the case.
> Calling it ->remove_bdev() is imo the correct thing because it gives
> block based filesystem the ability to handle device events how they see
> fit.
> 
> Once we will have non-block based filesystems that need a method to
> always shut down the filesystem itself we might have to revisit this
> design anyway but no one had that use-case yet.

I'm not sure what non-block file systems would need it for except
maybe for a generic IOC_SHUTDOWN implementation, but that would have
a different signature anyway as it needs to pass flags that don't
fit here.  So that would be a separate method.


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  parent reply	other threads:[~2025-07-10 10:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1751589725.git.wqu@suse.com>
2025-07-04  0:42 ` [f2fs-dev] [PATCH v4 1/6] fs: enhance and rename shutdown() callback to remove_bdev() Qu Wenruo via Linux-f2fs-devel
2025-07-04  9:00   ` [f2fs-dev] (subset) " Christian Brauner via Linux-f2fs-devel
2025-07-04  9:05   ` [f2fs-dev] " Jan Kara
2025-07-07 23:02   ` Dave Chinner via Linux-f2fs-devel
2025-07-07 23:22     ` Qu Wenruo via Linux-f2fs-devel
2025-07-08  0:45       ` Darrick J. Wong via Linux-f2fs-devel
2025-07-08  2:09         ` Qu Wenruo via Linux-f2fs-devel
2025-07-08  3:06           ` Qu Wenruo via Linux-f2fs-devel
2025-07-08  5:05             ` Dave Chinner via Linux-f2fs-devel
2025-07-08  5:41               ` Qu Wenruo via Linux-f2fs-devel
2025-07-08  7:55         ` Christian Brauner via Linux-f2fs-devel
2025-07-08 22:59           ` Dave Chinner via Linux-f2fs-devel
2025-07-08 23:07             ` Qu Wenruo via Linux-f2fs-devel
2025-07-09  0:35               ` Kent Overstreet
2025-07-09  0:55                 ` Qu Wenruo via Linux-f2fs-devel
2025-07-09  1:13                   ` Kent Overstreet
2025-07-10  8:33             ` Christian Brauner via Linux-f2fs-devel
2025-07-10 10:54           ` Christoph Hellwig [this message]
2025-07-08 10:20         ` Jan Kara
2025-07-08 20:20           ` Darrick J. Wong via Linux-f2fs-devel
2025-07-08 22:12             ` Qu Wenruo via Linux-f2fs-devel
2025-07-10  8:40             ` Christian Brauner via Linux-f2fs-devel
2025-07-10  9:54               ` Qu Wenruo via Linux-f2fs-devel
2025-07-11  9:34                 ` Christian Brauner via Linux-f2fs-devel
2025-07-10 10:52         ` Christoph Hellwig
2025-07-09 17:23 Jan Kara
2025-07-09 17:49 ` Kent Overstreet
2025-07-10 13:10   ` Jan Kara
2025-07-10 18:41     ` Kent Overstreet
2025-07-11 14:20       ` Jan Kara

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=aG-b0UiIEX4G2-UC@infradead.org \
    --to=hch@infradead.org \
    --cc=brauner@kernel.org \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=viro@zeniv.linux.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).