mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 for v7.2] vfs fixes
Date: Fri, 14 Aug 2026 15:05:58 +0200	[thread overview]
Message-ID: <20260814-vfs-7.2-rc8.fixes-6d7ba75b0b43@brauner> (raw)

Hey Linus,

/* Summary */

This contains last fixes for the current development cycle:

- Don't warn when a mount is completed from another user namespace.

  fsopen() records the caller's user namespace in fc->user_ns and hands
  back an ordinary file descriptor. The task that calls
  fsconfig(FSCONFIG_CMD_CREATE) doesn't have to be the one that created
  the context, and mount_capable() lets it through as long as the caller
  has CAP_SYS_ADMIN over fc->user_ns, which anyone in an ancestor
  namespace does. So fc->user_ns != current_user_ns() is something an
  unprivileged user can arrange.

  Both overlayfs and binfmt_misc WARN_ON() that. Overlayfs already
  has the same check as a plain error return in ovl_parse_param(). Drop
  the WARN_ON() and just refuse. Add selftests for both cases.

- Reject pid allocations through dead ancestor pid namespaces.

  Require PIDNS_ADDING in every namespace that will receive the pid
  before publishing any of them. That preserves the invariant that
  free_pid() never decrements pid_allocated in a namespace whose
  child_reaper is no longer live. The existing ENOMEM behavior is
  unchanged.

/* Conflicts */

Merge conflicts with mainline
=============================

No known conflicts.

Merge conflicts with other trees
================================

No known conflicts.

The following changes since commit db2ddb87143519e20a95aa36c60b36107b736a58:

  Linux 7.2-rc7 (2026-08-09 14:54:50 -0700)

are available in the Git repository at:

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.2-rc8.fixes

for you to fetch changes up to b64a9f67e082e04835ddd69d422a25168d69375b:

  pid: reject allocations through dead ancestor pid namespaces (2026-08-12 12:56:30 +0200)

----------------------------------------------------------------
vfs-7.2-rc8.fixes

Please consider pulling these changes from the signed vfs-7.2-rc8.fixes tag.

Thanks!
Christian

----------------------------------------------------------------
Christian Brauner (4):
      ovl: don't warn when the mount is completed from another user namespace
      binfmt_misc: don't warn when the mount is completed from another user namespace
      selftests/filesystems: test completing a context from another user namespace
      Merge patch series "fs: don't warn when a mount is completed from another user namespace"

Jérémy Jean (1):
      pid: reject allocations through dead ancestor pid namespaces

 fs/binfmt_misc.c                                   |   3 +-
 fs/overlayfs/super.c                               |   3 +-
 kernel/pid.c                                       |   6 +-
 tools/testing/selftests/Makefile                   |   1 +
 .../selftests/filesystems/fscontext_ns/Makefile    |  10 +
 .../filesystems/fscontext_ns/fscontext_ns_test.c   | 239 +++++++++++++++++++++
 6 files changed, 258 insertions(+), 4 deletions(-)
 create mode 100644 tools/testing/selftests/filesystems/fscontext_ns/Makefile
 create mode 100644 tools/testing/selftests/filesystems/fscontext_ns/fscontext_ns_test.c

             reply	other threads:[~2026-08-14 13:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 13:05 Christian Brauner [this message]
2026-08-14 15:59 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-08-02  9:31 Christian Brauner
2026-08-02 17:51 ` pr-tracker-bot
2026-07-26 15:37 Christian Brauner
2026-07-26 19:59 ` pr-tracker-bot
2026-07-03 11:32 Christian Brauner
2026-07-03 15:55 ` 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=20260814-vfs-7.2-rc8.fixes-6d7ba75b0b43@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®