diff options
author | Aleksa Sarai <cyphar@cyphar.com> | 2025-08-06 16:07:06 +1000 |
---|---|---|
committer | Christian Brauner <brauner@kernel.org> | 2025-08-11 14:52:40 +0200 |
commit | 807602d8cfc8b63e2c645fbbc66c8e82479ee311 (patch) | |
tree | 76dd488130564573c089e9cba35505d97b09c86f /scripts/gdb/linux/proc.py | |
parent | ad7fe23b4b0dc0c26187df92a5649948ef7049fa (diff) |
vfs: output mount_too_revealing() errors to fscontext
It makes little sense for fsmount() to output the warning message when
mount_too_revealing() is violated to kmsg. Instead, the warning should
be output (with a "VFS" prefix) to the fscontext log. In addition,
include the same log message for mount_too_revealing() when doing a
regular mount for consistency.
With the newest fsopen()-based mount(8) from util-linux, the error
messages now look like
# mount -t proc proc /tmp
mount: /tmp: fsmount() failed: VFS: Mount too revealing.
dmesg(1) may have more information after failed mount system call.
which could finally result in mount_too_revealing() errors being easier
for users to detect and understand.
Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
Link: https://lore.kernel.org/20250806-errorfc-mount-too-revealing-v2-2-534b9b4d45bb@cyphar.com
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'scripts/gdb/linux/proc.py')
0 files changed, 0 insertions, 0 deletions