linux-ext4 - [Bug 219132] Redundant "re-mounted ro" message

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-219132-13602-iWIiqR0MYh@https.bugzilla.kernel.org/>
Date: Wed, 07 Aug 2024 03:33:16 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 219132] Redundant "re-mounted ro" message

https://bugzilla.kernel.org/show_bug.cgi?id=219132

Theodore Tso (tytso@....edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@....edu

--- Comment #2 from Theodore Tso (tytso@....edu) ---
The suggestion in #1 isn't necessarily correct, though, because we could be
remounting to change some other superblock options.  For example:

mount -o remount,errors=continue /dev/vdc

Fundamentally, whenever runs "mount -o remount ...", we issue the "EXT4-fs
(DEVICE): re-mounted ..." message.   The fact that we print the ro/rw and quota
mode is completely arbitrary and more due to historical reasons than anything
else.   For example, the fact that we print the quota mode is pretty much
useless in this day and era and there are plenty of other mount option/state
that would probably be much more useful.

So the fact that we print the ro/rw state doesn't imply that it has changed. 
For example, if the file system is mounted read/write and we change the errors=
mode from continue to remount-ro, etc., we will print:

EXT4-fs (nvme0n1p3): re-mounted UUID rw. Quota mode: none.

... and it doesn't mean that we changed the rw/ro mode from ro to r/w.   

Should we change the behavior to something else?   Perhaps, although to be
honest it's not the highest priority thing for me.   I could see dropping the
quota mode and only printing the message when the r/o state changes.  Or maybe
we display any mount option that changes (which would be a lot more work).  Is
it worth the effort?  Meh.....
.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.