From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org
Cc: "Amir Goldstein" <amir73il@gmail.com>,
"Josef Bacik" <josef@toxicpanda.com>,
"Jeff Layton" <jlayton@kernel.org>, "Mike Yuan" <me@yhndnzj.com>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
"Lennart Poettering" <mzxreary@0pointer.de>,
"Aleksa Sarai" <cyphar@cyphar.com>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Jan Kara" <jack@suse.cz>, "Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
cgroups@vger.kernel.org, netdev@vger.kernel.org,
"Christian Brauner" <brauner@kernel.org>
Subject: [PATCH 0/3] ns: tweak ns common handling
Date: Wed, 24 Sep 2025 13:33:57 +0200 [thread overview]
Message-ID: <20250924-work-namespaces-fixes-v1-0-8fb682c8678e@kernel.org> (raw)
This contains three minor tweaks for namespace handling:
* Make struct ns_tree private. There's no need for anything to access
that directly.
* Drop a debug assert that would trigger in conditions that are benign.
* Move the type of the namespace out of struct proc_ns_operations and
into struct ns_common. This eliminates a pointer dereference and also
allows assertions to work when the namespace type is disabled and the
operations field set to NULL.
"Trust me, just one more fixes series, bro. Just one more, bro."
Signed-off-by: Christian Brauner <brauner@kernel.org>
---
Christian Brauner (3):
nstree: make struct ns_tree private
ns: move ns type into struct ns_common
ns: drop assert
fs/namespace.c | 6 +++---
fs/nsfs.c | 18 +++++++++---------
include/linux/ns_common.h | 30 +++++++++++++++++++++++++-----
include/linux/nstree.h | 13 -------------
include/linux/proc_ns.h | 1 -
init/version-timestamp.c | 1 +
ipc/msgutil.c | 1 +
ipc/namespace.c | 1 -
kernel/cgroup/cgroup.c | 1 +
kernel/cgroup/namespace.c | 1 -
kernel/nscommon.c | 7 +++----
kernel/nsproxy.c | 4 ++--
kernel/nstree.c | 21 +++++++++++++++++----
kernel/pid.c | 1 +
kernel/pid_namespace.c | 2 --
kernel/time/namespace.c | 3 +--
kernel/user.c | 1 +
kernel/user_namespace.c | 1 -
kernel/utsname.c | 1 -
net/core/net_namespace.c | 1 -
20 files changed, 65 insertions(+), 50 deletions(-)
---
base-commit: d969328c513c6679b4be11a995ffd4d184c25b34
change-id: 20250924-work-namespaces-fixes-99d0c1ce2d86
next reply other threads:[~2025-09-24 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 11:33 Christian Brauner [this message]
2025-09-24 11:33 ` [PATCH 1/3] nstree: make struct ns_tree private Christian Brauner
2025-09-24 11:46 ` Jan Kara
2025-09-24 22:39 ` kernel test robot
2025-09-24 11:33 ` [PATCH 2/3] ns: move ns type into struct ns_common Christian Brauner
2025-09-24 11:58 ` Jan Kara
2025-09-24 11:34 ` [PATCH 3/3] ns: drop assert Christian Brauner
2025-09-24 12:00 ` Jan Kara
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=20250924-work-namespaces-fixes-v1-0-8fb682c8678e@kernel.org \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=anna-maria@linutronix.de \
--cc=cgroups@vger.kernel.org \
--cc=cyphar@cyphar.com \
--cc=frederic@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=me@yhndnzj.com \
--cc=mkoutny@suse.com \
--cc=mzxreary@0pointer.de \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zbyszek@in.waw.pl \
/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;
as well as URLs for NNTP newsgroup(s).