aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2025-08-08 15:24:00 +0200
committerChristian Brauner <brauner@kernel.org>2025-08-11 14:52:41 +0200
commitbfa8ee11dc13b63041b90cc16d694f69c4747490 (patch)
tree76dd488130564573c089e9cba35505d97b09c86f /tools/perf/scripts/python
parentMerge patch series "fs: Remove old mount API helpers" (diff)
parentvfs: output mount_too_revealing() errors to fscontext (diff)
downloadlinux-bfa8ee11dc13b63041b90cc16d694f69c4747490.tar.gz
linux-bfa8ee11dc13b63041b90cc16d694f69c4747490.zip
Merge patch series "vfs: output mount_too_revealing() errors to fscontext"
Aleksa Sarai <cyphar@cyphar.com> says: 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. * patches from https://lore.kernel.org/20250806-errorfc-mount-too-revealing-v2-0-534b9b4d45bb@cyphar.com: vfs: output mount_too_revealing() errors to fscontext fscontext: add custom-prefix log helpers Link: https://lore.kernel.org/20250806-errorfc-mount-too-revealing-v2-0-534b9b4d45bb@cyphar.com Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions