From: Christian Brauner <brauner@kernel.org>
To: Ismael Luceno <ismael@iodev.co.uk>,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>, Chris Mason <mason@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd
Date: Fri, 20 Nov 2026 13:13:27 +0100 [thread overview]
Message-ID: <20261120-rentier-einfuhr-riefen-31ec13d7abf5@brauner> (raw)
In-Reply-To: <20261116224316.11237-10-ismael@iodev.co.uk>
On Mon, Nov 16, 2026 at 11:43:16PM +0100, Ismael Luceno wrote:
> This series lets btrfs assemble such a root filesystem in the kernel:
>
> * mount devtmpfs on the initial root before the root filesystem, so
> device nodes exist to open the other devices by name (init);
> * let a filesystem tell whether it is mounting the root device and read
> rootwait, and resolve root=UUID=/root=LABEL= values that name the
> filesystem rather than a partition (init/VFS);
Nope, sorry. The init and VFS parts of this are not acceptable. Scanning
for devices and resolving filesystem UUIDs and labels is exactly what an
initramfs is for. That's userspace policy and it doesn't belong in the
kernel.
The kernel can already find its root without an initrd: root=PARTUUID=
and root=PARTLABEL=. If you need a multi-device root, use an initramfs.
A ->find_by_spec() method in struct file_system_type that only exists to
parse root= isn't going to happen either. And with BTRFS_ROOT_SCAN
defaulting to y and selecting DEVTMPFS, 2/8 changes early boot for
everyone who has btrfs enabled.
So I agree with Qu.
prev parent reply other threads:[~2026-11-20 12:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 22:43 Ismael Luceno
2026-11-16 22:43 ` [PATCH 1/8] btrfs: add config options for the root device scan Ismael Luceno
2026-11-16 22:43 ` [PATCH 2/8] init: mount devtmpfs before the root filesystem Ismael Luceno
2026-11-16 22:43 ` [PATCH 3/8] init: let filesystems ask whether they are mounting the root device Ismael Luceno
2026-11-17 7:41 ` kernel test robot
2026-11-16 22:43 ` [PATCH 4/8] btrfs: add a helper to scan all block devices Ismael Luceno
2026-11-17 13:10 ` kernel test robot
2026-11-16 22:43 ` [PATCH 5/8] btrfs: wait for the root filesystem to have all its devices Ismael Luceno
2026-11-18 1:19 ` kernel test robot
2026-11-16 22:43 ` [PATCH 6/8] Documentation: btrfs: document waiting for the root filesystem devices Ismael Luceno
2026-11-16 22:43 ` [PATCH 7/8] init: let a filesystem resolve a root device by UUID or label Ismael Luceno
2026-11-16 22:43 ` [PATCH 8/8] btrfs: resolve root=UUID= and root=LABEL= Ismael Luceno
2026-11-16 23:41 ` [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd Qu Wenruo
2026-11-17 17:36 ` Ismael Luceno
2026-11-17 20:00 ` Qu Wenruo
2026-11-18 12:07 ` Ismael Luceno
2026-11-18 20:33 ` Qu Wenruo
2026-11-20 12:13 ` Christian Brauner [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=20261120-rentier-einfuhr-riefen-31ec13d7abf5@brauner \
--to=brauner@kernel.org \
--cc=dsterba@suse.com \
--cc=ismael@iodev.co.uk \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®