From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL 02/12 for v6.18] mount
Date: Fri, 26 Sep 2025 16:18:56 +0200 [thread overview]
Message-ID: <20250926-vfs-mount-743c2ca07c6b@brauner> (raw)
In-Reply-To: <20250926-vfs-618-e880cf3b910f@brauner>
Hey Linus,
/* Summary */
This contains some work around mount api handling:
* Output the warning message for mnt_too_revealing() triggered during
fsmount() to the fscontext log. This makes it possible for the mount
tool to output appropriate warnings on the command line. For example,
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.
* Do not consume fscontext log entries when returning -EMSGSIZE
Userspace generally expects APIs that return -EMSGSIZE to allow for
them to adjust their buffer size and retry the operation. However, the
fscontext log would previously clear the message even in the -EMSGSIZE
case.
Given that it is very cheap for us to check whether the buffer is too
small before we remove the message from the ring buffer, let's just do
that instead.
* Drop an unused argument from do_remount().
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3+b1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
[1] https://lore.kernel.org/linux-next/aNO0BKAXphoFEgUk@finisterre.sirena.org.uk
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.18-rc1.mount
for you to fetch changes up to 1e5f0fb41fccf5ecbb5506551790335c9578e320:
vfs: fs/namespace.c: remove ms_flags argument from do_remount (2025-08-11 16:08:31 +0200)
Please consider pulling these changes from the signed vfs-6.18-rc1.mount tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.18-rc1.mount
----------------------------------------------------------------
Aleksa Sarai (4):
fscontext: add custom-prefix log helpers
vfs: output mount_too_revealing() errors to fscontext
fscontext: do not consume log entries when returning -EMSGSIZE
selftests/filesystems: add basic fscontext log tests
Askar Safin (1):
vfs: fs/namespace.c: remove ms_flags argument from do_remount
Christian Brauner (3):
Merge patch series "fs: Remove old mount API helpers"
Merge patch series "vfs: output mount_too_revealing() errors to fscontext"
Merge patch series "fscontext: do not consume log entries when returning -EMSGSIZE"
Pedro Falcato (3):
fs: Remove mount_nodev
fs: Remove mount_bdev
docs/vfs: Remove mentions to the old mount API helpers
Documentation/filesystems/vfs.rst | 27 +----
fs/fsopen.c | 70 +++++++------
fs/namespace.c | 10 +-
fs/super.c | 63 ------------
include/linux/fs.h | 6 --
include/linux/fs_context.h | 18 +++-
tools/testing/selftests/filesystems/.gitignore | 1 +
tools/testing/selftests/filesystems/Makefile | 2 +-
tools/testing/selftests/filesystems/fclog.c | 130 +++++++++++++++++++++++++
9 files changed, 192 insertions(+), 135 deletions(-)
create mode 100644 tools/testing/selftests/filesystems/fclog.c
next prev parent reply other threads:[~2025-09-26 14:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 14:18 [GIT PULL 00/12 for v6.18] vfs 6.18 Christian Brauner
2025-09-26 14:18 ` [GIT PULL 01/12 for v6.18] misc Christian Brauner
2025-09-29 9:47 ` Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` Christian Brauner [this message]
2025-09-29 19:31 ` [GIT PULL 02/12 for v6.18] mount pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 03/12 for v6.18] inode Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 04/12 for v6.18] iomap Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 05/12 for v6.18] pidfs Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-10-01 14:18 ` Oleg Nesterov
2025-10-06 13:48 ` Christian Brauner
2025-10-07 14:34 ` Oleg Nesterov
2025-10-10 11:00 ` Christian Brauner
2025-09-26 14:19 ` [GIT PULL 06/12 for v6.18] rust Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 07/12 for v6.18] workqueue Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 08/12 for v6.18] core kernel Christian Brauner
2025-09-27 12:19 ` Sasha Levin
2025-09-29 9:53 ` Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 9/12 for v6.18] afs Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 10/12 for v6.18] namespaces Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 11/12 for v6.18] writeback Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 12/12 for v6.18] async directory preliminaries Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250926-vfs-mount-743c2ca07c6b@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®