From: Christian Brauner Date: Fri, 8 Aug 2025 13:24:00 +0000 (+0200) Subject: Merge patch series "vfs: output mount_too_revealing() errors to fscontext" X-Git-Tag: v6.18-rc1~240^2~2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=bfa8ee11dc13b63041b90cc16d694f69c4747490;p=thirdparty%2Flinux.git Merge patch series "vfs: output mount_too_revealing() errors to fscontext" Aleksa Sarai 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 --- bfa8ee11dc13b63041b90cc16d694f69c4747490