From: Askar Safin <safinaskar@gmail.com>
To: hpa@zytor.com
Cc: brauner@kernel.org, corbet@lwn.net, jack@suse.cz,
lennart@poettering.net, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
systemd-devel@lists.freedesktop.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH 0/3] Add the ability to mount filesystems during initramfs expansion
Date: Sat, 24 Jan 2026 20:41:50 +0300 [thread overview]
Message-ID: <20260124174150.974899-1-safinaskar@gmail.com> (raw)
In-Reply-To: <20260124003939.426931-1-hpa@zytor.com>
"H. Peter Anvin" <hpa@zytor.com>:
> At Plumber's 2024, Lennart Poettering of the systemd project requested
> the ability to overmount the rootfs with a separate tmpfs before
> initramfs expansion, so the populated tmpfs can be unmounted.
This is already solved by [1] and [2]. They are in next.
[1] https://lore.kernel.org/all/20251229-work-empty-namespace-v1-0-bfb24c7b061f@kernel.org/
[2] https://lore.kernel.org/all/20260112-work-immutable-rootfs-v2-0-88dd1c34a204@kernel.org/
--
Askar Safin
next prev parent reply other threads:[~2026-01-24 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 0:39 [PATCH 0/3] Add the ability to mount filesystems during initramfs expansion H. Peter Anvin
2026-01-24 0:39 ` [RFC PATCH 1/3] fs/init: move creating the mount data_page into init_mount() H. Peter Anvin
2026-01-24 0:39 ` [RFC PATCH 2/3] initramfs: support mounting filesystems during initramfs expansion H. Peter Anvin
2026-01-24 0:39 ` [RFC PATCH 3/3] Documentation/initramfs: document mount points in initramfs H. Peter Anvin
2026-01-24 17:41 ` Askar Safin [this message]
2026-01-24 18:33 ` [PATCH 0/3] Add the ability to mount filesystems during initramfs expansion H. Peter Anvin
2026-01-25 0:07 ` H. Peter Anvin
2026-02-02 7:38 ` [EXT] [systemd-devel] " Windl, Ulrich
2026-02-03 16:11 ` H. Peter Anvin
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=20260124174150.974899-1-safinaskar@gmail.com \
--to=safinaskar@gmail.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=lennart@poettering.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=systemd-devel@lists.freedesktop.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