* [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd
@ 2026-11-16 22:43 Ismael Luceno
2026-11-16 22:43 ` [PATCH 2/8] init: mount devtmpfs before the root filesystem Ismael Luceno
` (3 more replies)
0 siblings, 4 replies; 8+ messages in thread
From: Ismael Luceno @ 2026-11-16 22:43 UTC (permalink / raw)
To: linux-kernel, linux-btrfs
Cc: Ismael Luceno, David Sterba, Chris Mason, Christian Brauner,
Alexander Viro, Jan Kara, linux-fsdevel, linux-doc
A multi-device btrfs root filesystem is normally assembled by the device
scanner that an initrd runs before mounting the root. Without an initrd
nothing runs that scanner, so the root mount names a single device and
the rest of the array is left out.
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);
* scan all block devices for the remaining members of a btrfs root
filesystem, and wait for all of them to appear before mounting.
The scan and wait are gated on CONFIG_BTRFS_ROOT_SCAN (default y) and
only act on the root mount when the user asked for it with rootwait, so
non-root mounts and systems without the option are unchanged.
Ismael Luceno (8):
btrfs: add config options for the root device scan
init: mount devtmpfs before the root filesystem
init: let filesystems ask whether they are mounting the root device
btrfs: add a helper to scan all block devices
btrfs: wait for the root filesystem to have all its devices
Documentation: btrfs: document waiting for the root filesystem devices
init: let a filesystem resolve a root device by UUID or label
btrfs: resolve root=UUID= and root=LABEL=
Documentation/filesystems/btrfs.rst | 31 +++++
fs/btrfs/Kconfig | 25 ++++
fs/btrfs/super.c | 165 +++++++++++++++++++++++
fs/btrfs/volumes.c | 196 ++++++++++++++++++++++++++++
fs/btrfs/volumes.h | 25 ++++
fs/filesystems.c | 37 ++++++
include/linux/fs.h | 10 ++
include/linux/root_dev.h | 14 ++
init/do_mounts.c | 51 +++++++-
9 files changed, 553 insertions(+), 1 deletion(-)
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH 2/8] init: mount devtmpfs before the root filesystem
2026-11-16 22:43 [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd Ismael Luceno
@ 2026-11-16 22:43 ` Ismael Luceno
2026-11-16 22:43 ` [PATCH 3/8] init: let filesystems ask whether they are mounting the root device Ismael Luceno
` (2 subsequent siblings)
3 siblings, 0 replies; 8+ messages in thread
From: Ismael Luceno @ 2026-11-16 22:43 UTC (permalink / raw)
To: linux-kernel
Cc: Ismael Luceno, Ismael Luceno, Alexander Viro, Christian Brauner,
Jan Kara, open list:FILESYSTEMS (VFS and infrastructure)
devtmpfs is mounted after the root filesystem, which leaves the root
mount with no /dev nodes to look devices up by. A filesystem that has
to open block devices other than the one it was given has nothing to
open them by, and without an initrd there is no userspace around to
create the nodes either.
Mount it on the initial root before the root filesystem is mounted, so
the root filesystem can resolve device paths. This is what lets a
multi-device btrfs root assemble itself with no initrd to run the
device scanner.
This mount is on the initial root and goes away with it at the pivot,
so the existing mount after mount_root() is kept: that is the one that
ends up in the new root.
This is only needed by the btrfs root device scan, so it is done only when
CONFIG_BTRFS_ROOT_SCAN is set; without it boot is unchanged.
Signed-off-by: Ismael Luceno <ismael@iodev.co.uk>
Signed-off-by: Ismael Luceno <iluceno@suse.de>
---
init/do_mounts.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/init/do_mounts.c b/init/do_mounts.c
index b088021b1546..febcc37f9128 100644
--- a/init/do_mounts.c
+++ b/init/do_mounts.c
@@ -480,6 +480,20 @@ #define CIFSROOT_RETRY_MAX 5
if (root_wait)
wait_for_root(saved_root_name);
+
+ /*
+ * Mount devtmpfs before the root filesystem, so that the filesystem
+ * mounting it can look devices up by path. A multi-device btrfs root
+ * needs this: it has to open its other devices to assemble the
+ * filesystem, and there is no userspace around to create the nodes.
+ *
+ * This one is on the initial root and goes away with it below; the
+ * mount after mount_root() is the one that sticks around. Only the
+ * btrfs root device scan needs it.
+ */
+ if (IS_ENABLED(CONFIG_BTRFS_ROOT_SCAN))
+ devtmpfs_mount();
+
mount_root(saved_root_name);
devtmpfs_mount();
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 3/8] init: let filesystems ask whether they are mounting the root device
2026-11-16 22:43 [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd Ismael Luceno
2026-11-16 22:43 ` [PATCH 2/8] init: mount devtmpfs before the root filesystem Ismael Luceno
@ 2026-11-16 22:43 ` Ismael Luceno
2026-11-17 7:41 ` kernel test robot
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 23:41 ` [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd Qu Wenruo
3 siblings, 1 reply; 8+ messages in thread
From: Ismael Luceno @ 2026-11-16 22:43 UTC (permalink / raw)
To: linux-kernel
Cc: Ismael Luceno, Ismael Luceno, Alexander Viro, Christian Brauner,
Jan Kara, open list:FILESYSTEMS (VFS and infrastructure)
A filesystem that wants to treat the root mount differently from any
other mount has no way to tell which one it is being asked for, and no
way to find out how long the user is willing to wait for it. Expose
both.
root_wait becomes a global so a filesystem can read the value the user
gave rootwait=, and is_root_dev() reports whether a device is the one
the root filesystem is being mounted from. mount_root() is the only
thing that mounts from /dev/root, and that name exists for the root
mount alone, so a filesystem handed that device is being asked to be
the root filesystem.
No behaviour changes. This is here so a filesystem can act on the
root mount, which btrfs does next.
Signed-off-by: Ismael Luceno <ismael@iodev.co.uk>
Signed-off-by: Ismael Luceno <iluceno@suse.de>
---
include/linux/root_dev.h | 14 ++++++++++++++
init/do_mounts.c | 18 +++++++++++++++++-
2 files changed, 31 insertions(+), 1 deletion(-)
diff --git a/include/linux/root_dev.h b/include/linux/root_dev.h
index 847c9a06101b..b5a0181d1967 100644
--- a/include/linux/root_dev.h
+++ b/include/linux/root_dev.h
@@ -15,4 +15,18 @@ #define _ROOT_DEV_H_
extern dev_t ROOT_DEV;
+/*
+ * Milliseconds to wait for the root device, from the rootwait= parameter.
+ * Negative means wait indefinitely, zero means do not wait.
+ */
+extern int root_wait;
+
+/*
+ * True if @dev is the device the root filesystem is being mounted from, or
+ * was mounted from. The root mount names the device /dev/root, which is
+ * created for it alone, so a filesystem can tell the root mount from any
+ * other it is asked to do.
+ */
+bool is_root_dev(dev_t dev);
+
#endif
diff --git a/init/do_mounts.c b/init/do_mounts.c
index febcc37f9128..f1dcb18201eb 100644
--- a/init/do_mounts.c
+++ b/init/do_mounts.c
@@ -30,9 +30,9 @@
int root_mountflags = MS_RDONLY | MS_SILENT;
static char __initdata saved_root_name[64];
-static int root_wait;
dev_t ROOT_DEV;
+int root_wait;
static int __init readonly(char *str)
{
@@ -372,10 +372,26 @@ #define CIFSROOT_RETRY_MAX 5
pr_emerg("Failed to create /dev/root: %d\n", err);
mount_root_generic("/dev/root", root_device_name, root_mountflags);
}
+
+/*
+ * Was the filesystem on @dev mounted as the root filesystem? mount_root()
+ * above is the only thing that mounts from /dev/root, and that name is given
+ * to the root mount alone, so a filesystem being handed that device is being
+ * asked to be the root filesystem.
+ */
+bool is_root_dev(dev_t dev)
+{
+ return dev && dev == ROOT_DEV;
+}
#else
static inline void mount_block_root(char *root_device_name)
{
}
+
+static inline bool is_root_dev(dev_t dev)
+{
+ return false;
+}
#endif /* CONFIG_BLOCK */
void __init mount_root(char *root_device_name)
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 7/8] init: let a filesystem resolve a root device by UUID or label
2026-11-16 22:43 [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd 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-16 22:43 ` Ismael Luceno
2026-11-16 23:41 ` [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd Qu Wenruo
3 siblings, 0 replies; 8+ messages in thread
From: Ismael Luceno @ 2026-11-16 22:43 UTC (permalink / raw)
To: linux-kernel
Cc: Ismael Luceno, Ismael Luceno, Alexander Viro, Christian Brauner,
Jan Kara, open list:FILESYSTEMS (VFS and infrastructure)
root= takes PARTUUID= and PARTLABEL=, both of which come from the
partition table, and so can be resolved by the block layer alone.
UUID= and LABEL= name the filesystem, and a filesystem UUID and label
live in its superblock. Nothing outside the filesystem can recognise
one, so without this a "root=UUID=..." is taken for a device name,
fails to resolve, and — because that failure is indistinguishable
from a bad device name — takes rootwait down with it on the way past.
Let each registered filesystem look for its own UUID or label, and ask
them in turn until one claims the value. Filesystems that do not
implement it cost nothing, so this is inert for every filesystem that
has no use for it.
The lookup opens and reads devices, so it can sleep; take a module
reference for as long as the filesystem is in use, as the comment on
file_systems describes.
Signed-off-by: Ismael Luceno <ismael@iodev.co.uk>
Signed-off-by: Ismael Luceno <iluceno@suse.de>
---
fs/filesystems.c | 37 +++++++++++++++++++++++++++++++++++++
include/linux/fs.h | 10 ++++++++++
init/do_mounts.c | 19 +++++++++++++++++++
3 files changed, 66 insertions(+)
diff --git a/fs/filesystems.c b/fs/filesystems.c
index 3083d904df9b..13e509e027d6 100644
--- a/fs/filesystems.c
+++ b/fs/filesystems.c
@@ -240,6 +240,43 @@ SYSCALL_DEFINE3(sysfs, int, option, unsigned long, arg1, unsigned long, arg2)
return count;
}
+/**
+ * find_dev_by_fs_spec - find the block device holding a filesystem by UUID or label
+ * @key: what @value is, "UUID" or "LABEL"
+ * @value: the filesystem UUID, or its label
+ *
+ * A filesystem UUID and label live in the superblock rather than in the
+ * partition metadata, so unlike PARTUUID= and PARTLABEL= they cannot be
+ * resolved from the partition table: the filesystem that knows them has to be
+ * asked. Offer the value to each registered filesystem until one claims it.
+ *
+ * Return the dev_t found, or 0 if no filesystem recognised it.
+ */
+dev_t find_dev_by_fs_spec(const char *key, const char *value)
+{
+ struct file_system_type *p;
+ dev_t dev = 0;
+
+ guard(rcu)();
+ hlist_for_each_entry_rcu(p, &file_systems, list) {
+ if (!(p->fs_flags & FS_REQUIRES_DEV) || !p->find_by_spec)
+ continue;
+ /*
+ * The lookup reads devices and so may sleep; hold a module
+ * reference for as long as we use p, as the comment on
+ * file_systems above describes.
+ */
+ if (!try_module_get(p->owner))
+ continue;
+ if (p->find_by_spec(key, value, &dev) && dev)
+ break;
+ module_put(p->owner);
+ }
+
+ return dev;
+}
+EXPORT_SYMBOL_GPL(find_dev_by_fs_spec);
+
#ifdef CONFIG_PROC_FS
static void invalidate_filesystems_string(void)
{
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 5b3a100aba77..9267ae28dc36 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -2308,6 +2308,15 @@ #define FS_USERNS_DELEGATABLE 1024 /* Can be mounted inside userns from outside
#define FS_DISALLOW_NOTIFY 2048 /* No fsnotify marks on its objects */
#define FS_RENAME_DOES_D_MOVE 32768 /* FS will handle d_move() during rename() internally. */
int (*init_fs_context)(struct fs_context *);
+ /*
+ * Look for the block device holding the filesystem that @key
+ * identifies as @value, for "root=UUID=" and "root=LABEL=". Both live
+ * in the superblock rather than in the partition metadata, so unlike
+ * PARTUUID= and PARTLABEL= it is the filesystem that has to recognise
+ * them. @key is "UUID" or "LABEL". Set *dev and return 0 on a
+ * match, or return an error if there is none.
+ */
+ int (*find_by_spec)(const char *key, const char *value, dev_t *dev);
const struct fs_parameter_spec *parameters;
void (*kill_sb) (struct super_block *);
struct module *owner;
@@ -3579,6 +3588,7 @@ #define DEFINE_SIMPLE_ATTRIBUTE_SIGNED(__fops, __get, __set, __fmt) \
size_t len, loff_t *ppos);
int __init list_bdev_fs_names(char *buf, size_t size);
+dev_t find_dev_by_fs_spec(const char *key, const char *value);
#define __FMODE_EXEC ((__force int) FMODE_EXEC)
diff --git a/init/do_mounts.c b/init/do_mounts.c
index f1dcb18201eb..3845b1e67f46 100644
--- a/init/do_mounts.c
+++ b/init/do_mounts.c
@@ -453,6 +453,25 @@ #define CIFSROOT_RETRY_MAX 5
return Root_NFS;
if (strcmp(root_device_name, "/dev/cifs") == 0)
return Root_CIFS;
+
+ /*
+ * A filesystem UUID or label is in the superblock, not in the
+ * partition table, so it is the filesystem that has to recognise it.
+ * Try that before early_lookup_bdev(), which would take "UUID=..." for
+ * a device name and fail.
+ */
+ if (!strncmp(root_device_name, "UUID=", 5)) {
+ dev = find_dev_by_fs_spec("UUID", root_device_name + 5);
+ if (dev)
+ return dev;
+ return 0;
+ }
+ if (!strncmp(root_device_name, "LABEL=", 6)) {
+ dev = find_dev_by_fs_spec("LABEL", root_device_name + 6);
+ if (dev)
+ return dev;
+ return 0;
+ }
if (strcmp(root_device_name, "/dev/ram") == 0)
return Root_RAM0;
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd
2026-11-16 22:43 [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd Ismael Luceno
` (2 preceding siblings ...)
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 23:41 ` Qu Wenruo
2026-11-17 17:36 ` Ismael Luceno
3 siblings, 1 reply; 8+ messages in thread
From: Qu Wenruo @ 2026-11-16 23:41 UTC (permalink / raw)
To: Ismael Luceno, linux-kernel, linux-btrfs
Cc: David Sterba, Chris Mason, Christian Brauner, Alexander Viro,
Jan Kara, linux-fsdevel, linux-doc
在 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?
Multi-device filesystems/storage solution requires initramfs to do the
scan, no matter if it's btrfs or device-mapper, it's already the common
knowledge.
I just see no strong reasons to do this at all.
And Sashiko is already reporting over 10 high level problems, which is
not a good sign either.
> Without an initrd
> nothing runs that scanner, so the root mount names a single device and
> the rest of the array is left out.
>
> 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);
> * scan all block devices for the remaining members of a btrfs root
> filesystem, and wait for all of them to appear before mounting.
>
> The scan and wait are gated on CONFIG_BTRFS_ROOT_SCAN (default y) and
> only act on the root mount when the user asked for it with rootwait, so
> non-root mounts and systems without the option are unchanged.
>
>
> Ismael Luceno (8):
> btrfs: add config options for the root device scan
> init: mount devtmpfs before the root filesystem
> init: let filesystems ask whether they are mounting the root device
> btrfs: add a helper to scan all block devices
> btrfs: wait for the root filesystem to have all its devices
> Documentation: btrfs: document waiting for the root filesystem devices
> init: let a filesystem resolve a root device by UUID or label
> btrfs: resolve root=UUID= and root=LABEL=
>
> Documentation/filesystems/btrfs.rst | 31 +++++
> fs/btrfs/Kconfig | 25 ++++
> fs/btrfs/super.c | 165 +++++++++++++++++++++++
> fs/btrfs/volumes.c | 196 ++++++++++++++++++++++++++++
> fs/btrfs/volumes.h | 25 ++++
> fs/filesystems.c | 37 ++++++
> include/linux/fs.h | 10 ++
> include/linux/root_dev.h | 14 ++
> init/do_mounts.c | 51 +++++++-
> 9 files changed, 553 insertions(+), 1 deletion(-)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH 3/8] init: let filesystems ask whether they are mounting the root device
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
0 siblings, 0 replies; 8+ messages in thread
From: kernel test robot @ 2026-11-17 7:41 UTC (permalink / raw)
To: Ismael Luceno, linux-kernel
Cc: oe-kbuild-all, Ismael Luceno, Alexander Viro, Christian Brauner,
Jan Kara, open list:FILESYSTEMS (VFS and infrastructure)
Hi Ismael,
kernel test robot noticed the following build errors:
[auto build test ERROR on kdave/for-next]
[also build test ERROR on btrfs/for-next brauner-vfs/vfs.all linus/master v7.4-rc3 next-20261116]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ismael-Luceno/btrfs-add-config-options-for-the-root-device-scan/20261116-234317
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
patch link: https://lore.kernel.org/r/20261116224316.11237-13-ismael%40iodev.co.uk
patch subject: [PATCH 3/8] init: let filesystems ask whether they are mounting the root device
config: parisc-randconfig-1001-20261117 (https://download.01.org/0day-ci/archive/20261117/202611171523.oW7KTbJo-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261117/202611171523.oW7KTbJo-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202611171523.oW7KTbJo-lkp@intel.com/
All errors (new ones prefixed by >>):
>> init/do_mounts.c:391:20: error: static declaration of 'is_root_dev' follows non-static declaration
static inline bool is_root_dev(dev_t dev)
^~~~~~~~~~~
In file included from init/do_mounts.c:8:
include/linux/root_dev.h:30:6: note: previous declaration of 'is_root_dev' was here
bool is_root_dev(dev_t dev);
^~~~~~~~~~~
vim +/is_root_dev +391 init/do_mounts.c
390
> 391 static inline bool is_root_dev(dev_t dev)
392 {
393 return false;
394 }
395 #endif /* CONFIG_BLOCK */
396
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd
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
0 siblings, 1 reply; 8+ messages in thread
From: Ismael Luceno @ 2026-11-17 17:36 UTC (permalink / raw)
To: Qu Wenruo
Cc: linux-kernel, linux-btrfs, David Sterba, Chris Mason,
Christian Brauner, Alexander Viro, Jan Kara, linux-fsdevel,
linux-doc
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?
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd
2026-11-17 17:36 ` Ismael Luceno
@ 2026-11-17 20:00 ` Qu Wenruo
0 siblings, 0 replies; 8+ messages in thread
From: Qu Wenruo @ 2026-11-17 20:00 UTC (permalink / raw)
To: Ismael Luceno, Qu Wenruo
Cc: linux-kernel, linux-btrfs, David Sterba, Chris Mason,
Christian Brauner, Alexander Viro, Jan Kara, linux-fsdevel,
linux-doc
在 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?
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2026-11-17 20:00 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-16 22:43 [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd 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 7/8] init: let a filesystem resolve a root device by UUID or 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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox