Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: David Sterba <dsterba@suse.cz>
Cc: Jan Kara <jack@suse.cz>, David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Josef Bacik <josef@toxicpanda.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH RESEND] btrfs: use the super_block as holder when mounting file systems
Date: Tue, 26 Sep 2023 11:59:50 +0200	[thread overview]
Message-ID: <20230926-sehkraft-duldung-6b4ef0ddbb74@brauner> (raw)
In-Reply-To: <20230925161327.GP13697@twin.jikos.cz>

> > Next time we will ensure that a vfs triggered conversion must go through
> > a vfs tree as this half converted state with forgotten patches is not
> > something that we should repeat.
> 
> Taking this as an example, I really don't want to let such patches go
> through VFS git. I understand there are API-level cleanups done in
> VFS that require reorganizing code in the filesystems but IMO the
> conversions must be done in the filesystems first and the VFS cleanups
> as a followup.

Whether or not this order is possible depends on the patchset. If we do
VFS level conversions that impact all filesystems we will do changes to
all filesystems in one go if the changes need to be done all at the same
time as we have done many times in the past. There's really nothing new.

> there's a change regarding the reviews or merge.

We'll likely end pulling in the required btrfs changes from you anyway
so Jan's series isn't blocked indefinitely from getting testing in
-next.

  reply	other threads:[~2023-09-26  9:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 12:19 [PATCH RESEND] btrfs: use the super_block as holder when mounting file systems Jan Kara
2023-09-21 12:50 ` Christian Brauner
2023-09-21 13:07   ` Jan Kara
2023-09-21 13:33     ` Christian Brauner
2023-09-25 16:13   ` David Sterba
2023-09-26  9:59     ` Christian Brauner [this message]
2023-09-25 15:54 ` David Sterba
2023-09-26  9:45   ` Christian Brauner

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=20230926-sehkraft-duldung-6b4ef0ddbb74@brauner \
    --to=brauner@kernel.org \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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