diff options
| author | Nicolas Bretz <bretznic@gmail.com> | 2025-03-19 20:10:11 +0300 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2025-03-21 08:33:11 +0300 |
| commit | d7b0befd09320e3356a75cb96541c030515e7f5f (patch) | |
| tree | 4e8cad50468920fe28002da6d86779cad5b213b1 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 129245cfbd6d79c6d603f357f428010ccc0f0ee7 (diff) | |
| download | linux-d7b0befd09320e3356a75cb96541c030515e7f5f.tar.xz | |
ext4: on a remount, only log the ro or r/w state when it has changed
A user complained that a message such as:
EXT4-fs (nvme0n1p3): re-mounted UUID ro. Quota mode: none.
implied that the file system was previously mounted read/write and was
now remounted read-only, when it could have been some other mount
state that had changed by the "mount -o remount" operation. Fix this
by only logging "ro"or "r/w" when it has changed.
https://bugzilla.kernel.org/show_bug.cgi?id=219132
Signed-off-by: Nicolas Bretz <bretznic@gmail.com>
Link: https://patch.msgid.link/20250319171011.8372-1-bretznic@gmail.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions