public inbox for linux-fsdevel@vger.kernel.org
 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.1] kernel misc
Date: Tue, 14 Apr 2026 14:46:36 +0200	[thread overview]
Message-ID: <20260414-kernel-misc-v71-d07943689d03@brauner> (raw)
In-Reply-To: <20260410-vfs-v71-b055f260060c@brauner>

Hey Linus,

/* Summary */

Features

- pid_namespace: make init creation more flexible

  Annotate ->child_reaper accesses with {READ,WRITE}_ONCE() to protect
  the unlocked readers from cpu/compiler reordering, and enforce that
  pid 1 in a pid namespace is always the first allocated pid (the
  set_tid path already required this).

  On top of that, allow opening pid_for_children before the pid
  namespace init has been created. This lets one process create the
  pid namespace and a different process create the init via setns(),
  which makes clone3(set_tid) usable in all cases evenly and is
  particularly useful to CRIU when restoring nested containers.

  A new selftest covers both the basic create-pidns-then-init flow and
  the cross-process variant, and a MAINTAINERS entry for the pid
  namespace code is added.

Cleanups

- signal: update outdated comment for the removed freezable_schedule()

/* 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
================================

No known conflicts.

The following changes since commit 1f318b96cc84d7c2ab792fcc0bfd42a7ca890681:

  Linux 7.0-rc3 (2026-03-08 16:56:54 -0700)

are available in the Git repository at:

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/kernel-7.1-rc1.misc

for you to fetch changes up to 4c68d150246d7e1d826a807a82e6eb6b4669f42c:

  signal: update outdated comment for removed freezable_schedule() (2026-03-23 16:38:31 +0100)

----------------------------------------------------------------
kernel-7.1-rc1.misc

Please consider pulling these changes from the signed kernel-7.1-rc1.misc tag.

Thanks!
Christian

----------------------------------------------------------------
Christian Brauner (1):
      Merge patch series "pid_namespace: make init creation more flexible"

Kexin Sun (1):
      signal: update outdated comment for removed freezable_schedule()

Pavel Tikhomirov (5):
      pid_namespace: avoid optimization of accesses to ->child_reaper
      pid: check init is created first after idr alloc
      pid_namespace: allow opening pid_for_children before init was created
      selftests: Add tests for creating pidns init via setns
      MAINTAINERS: add a pid namespace entry

 MAINTAINERS                                        |  11 +-
 kernel/exit.c                                      |   3 +-
 kernel/fork.c                                      |   5 +-
 kernel/pid.c                                       |  19 +-
 kernel/pid_namespace.c                             |   9 -
 kernel/signal.c                                    |   5 +-
 tools/testing/selftests/pid_namespace/.gitignore   |   1 +
 tools/testing/selftests/pid_namespace/Makefile     |   2 +-
 .../selftests/pid_namespace/pidns_init_via_setns.c | 238 +++++++++++++++++++++
 9 files changed, 269 insertions(+), 24 deletions(-)
 create mode 100644 tools/testing/selftests/pid_namespace/pidns_init_via_setns.c

  parent reply	other threads:[~2026-04-14 12:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 15:15 [GIT PULL 00/12 for v7.1] v7.1 Christian Brauner
2026-04-10 15:16 ` [GIT PULL 01/12 for v7.1] vfs writeback Christian Brauner
2026-04-13 17:53   ` pr-tracker-bot
2026-04-10 15:16 ` [GIT PULL 02/12 for v7.1] vfs xattr Christian Brauner
2026-04-13 17:53   ` pr-tracker-bot
2026-04-10 15:16 ` [GIT PULL 03/12 for v7.1] vfs directory Christian Brauner
2026-04-13 17:53   ` pr-tracker-bot
2026-04-10 15:17 ` [GIT PULL 04/12 for v7.1] vfs integrity Christian Brauner
2026-04-13 17:53   ` pr-tracker-bot
2026-04-10 15:18 ` [GIT PULL 05/12 for v7.1] vfs fs_struct Christian Brauner
2026-04-13 19:18   ` Linus Torvalds
2026-04-14  9:52     ` Christian Brauner
2026-04-10 15:18 ` [GIT PULL 06/12 for v7.1] vfs kino Christian Brauner
2026-04-13 22:48   ` pr-tracker-bot
2026-04-10 15:19 ` [GIT PULL 07/12 for v7.1] vfs fat Christian Brauner
2026-04-13 22:48   ` pr-tracker-bot
2026-04-10 15:19 ` [GIT PULL 08/12 for v7.1] vfs bh metadata Christian Brauner
2026-04-13 22:48   ` pr-tracker-bot
2026-04-10 15:19 ` [GIT PULL 09/12 for v7.1] namespaces misc Christian Brauner
2026-04-13 22:48   ` pr-tracker-bot
2026-04-10 15:21 ` [GIT PULL 10/12 for v7.1] vfs pidfs Christian Brauner
2026-04-13 22:48   ` pr-tracker-bot
2026-04-10 15:21 ` [GIT PULL 11/12 for v7.1] vfs mount Christian Brauner
2026-04-13 21:17   ` Linus Torvalds
2026-04-14 10:58     ` Christian Brauner
2026-04-15  3:38       ` pr-tracker-bot
2026-04-10 15:23 ` [GIT PULL 12/12 for v7.1] vfs misc Christian Brauner
2026-04-13 22:48   ` pr-tracker-bot
2026-04-14 12:46 ` Christian Brauner [this message]
2026-04-15  3:38   ` [GIT PULL for v7.1] kernel misc 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=20260414-kernel-misc-v71-d07943689d03@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