From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Ismael Luceno <ismael@iodev.co.uk>, Qu Wenruo <wqu@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
David Sterba <dsterba@suse.com>, Chris Mason <mason@kernel.org>,
Christian Brauner <brauner@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: Wed, 18 Nov 2026 06:30:31 +1030 [thread overview]
Message-ID: <ce9f04e8-a5e6-478b-acf7-e2ad56e0c456@gmx.com> (raw)
In-Reply-To: <20261117183643.36afff2b@pirotess>
在 2026/11/18 04:06, Ismael Luceno 写道:
> On Tue, 17 Nov 2026 10:11:46 +1030
> Qu Wenruo <wqu@suse.com> wrote:
>> 在 2026/11/17 09:13, Ismael Luceno 写道:
>>> A multi-device btrfs root filesystem is normally assembled by the
>>> device scanner that an initrd runs before mounting the root.
>>
>> What is the problem here?
>>
>> Is generating an initramfs really that complex?
>
> Why depend on an initramfs?
Why not? One should not put everything into kernel.
E.g. what if the customer has some custom udev rules for devices names?
Now they can not use the custom devices names during boot, which they
can before.
Shouldn't this count as a regression?
prev parent reply other threads:[~2026-11-17 20:00 UTC|newest]
Thread overview: 14+ 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-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 [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=ce9f04e8-a5e6-478b-acf7-e2ad56e0c456@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=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 \
--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
all inboxes | Powered by JetHome®