]> git.ipfire.org Git - thirdparty/linux.git/commit
vfs: output mount_too_revealing() errors to fscontext
authorAleksa Sarai <cyphar@cyphar.com>
Wed, 6 Aug 2025 06:07:06 +0000 (16:07 +1000)
committerChristian Brauner <brauner@kernel.org>
Mon, 11 Aug 2025 12:52:40 +0000 (14:52 +0200)
commit807602d8cfc8b63e2c645fbbc66c8e82479ee311
tree76dd488130564573c089e9cba35505d97b09c86f
parentad7fe23b4b0dc0c26187df92a5649948ef7049fa
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>
fs/namespace.c