linux-kernel - Re: 2.6.0-test3-mm1 and rootflags

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20210629172053.1709-1-greg.depoire@gmail.com>
Date:   Tue, 29 Jun 2021 19:20:53 +0200
From:   Greg Depoire--Ferrer <greg.depoire@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Re: 2.6.0-test3-mm1 and rootflags

Hello.

I configure my kernel to boot without an initrd, with "rw root=PARTUUID=...
rootflags=...". I would like the kernel to mount my root partition with
MS_NOATIME but it is currently not possible without using an initrd that
remounts the root partition with the new flags, as was described in this
thread.

Because the kernel already supports setting filesystem dependent flags, I think
it would make sense for it to also support setting filesystem independent flags.
Also, there is the issue of flags that can't be reset later by initrd (see the
previous messages).

In reply to this message, there is a patch that implements what was suggested,
adding a 'rootopts=' parameter that takes a bitmap value for the mount flags.

It's my first time using a mailing list. I'm not sure if you're supposed to
reply to very old messages like this one or create a new thread instead. Sorry
if I did something wrong.