From: Rob Landley <rob@landley.net>
To: Lichen Liu <lichliu@redhat.com>,
viro@zeniv.linux.org.uk, brauner@kernel.org
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
weilongchen@huawei.com
Subject: Re: [PATCH] fs: Add 'rootfsflags' to set rootfs mount options
Date: Sat, 9 Aug 2025 10:02:09 -0500 [thread overview]
Message-ID: <feadab5e-915c-44ae-a1a2-46a2efc5f113@landley.net> (raw)
In-Reply-To: <20250808015134.2875430-2-lichliu@redhat.com>
On 8/7/25 20:51, Lichen Liu wrote:
> This patch introduces a new kernel command-line parameter, rootfsflags,
> which allows passing specific mount options directly to the rootfs when
> it is first mounted. This gives users control over the rootfs behavior.
Works for me. In an i486 mkroot build against stock 6.16 with this patch:
$ root/i486/run-qemu.sh
...
# grep rootfs /proc/mounts
rootfs / rootfs rw,size=125728k,nr_inodes=31432 0 0
# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 125728 764 124964 1% /
dev 125728 0 125728 0% /dev
$ KARGS="rootfsflags=size=1m" root/i486/run-qemu.sh
...
# grep rootfs /proc/mounts
rootfs / rootfs rw,size=1024k,nr_inodes=31432 0 0
# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1024 764 260 75% /
dev 125728 0 125728 0% /dev
Tested-by: Rob Landley <rob@landley.net>
Rob
next prev parent reply other threads:[~2025-08-09 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 1:51 Lichen Liu
2025-08-08 2:30 ` Dave Young
2025-08-08 2:47 ` Dave Young
2025-08-08 3:36 ` Lichen Liu
2025-08-08 17:59 ` Rob Landley
2025-08-11 1:57 ` Lichen Liu
2025-08-08 14:38 ` Rob Landley
2025-08-09 15:02 ` Rob Landley [this message]
2025-08-14 8:13 ` Askar Safin
2025-08-14 10:25 ` Lichen Liu
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=feadab5e-915c-44ae-a1a2-46a2efc5f113@landley.net \
--to=rob@landley.net \
--cc=brauner@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=lichliu@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=weilongchen@huawei.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®