From: Peter Zijlstra <peterz@infradead.org>
To: Nicholas Sielicki <linux@opensource.nslick.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Daniel Gomez <da.gomez@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Aaron Tomlin <atomlin@atomlin.com>,
Matthias Maennich <maennich@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-modules@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] module: expose imported namespaces via sysfs
Date: Sat, 7 Mar 2026 10:30:06 +0100 [thread overview]
Message-ID: <20260307093006.GU606826@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260307090010.20828-2-linux@opensource.nslick.com>
On Sat, Mar 07, 2026 at 03:00:09AM -0600, Nicholas Sielicki wrote:
> Previously, the only way for userspace to inspect the symbol
> namespaces a module imports is to locate the .ko on disk and invoke
> modinfo(8) to decompress/parse the metadata. The kernel validated
> namespaces at load time, but it was otherwise discarded.
>
> Add /sys/module/*/import_ns to expose imported namespaces for
> currently loaded modules. The file contains one namespace per line and
> only exists for modules that import at least one namespace.
What I'm missing here is why users would care about this?
next prev parent reply other threads:[~2026-03-07 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 9:00 [PATCH v2 0/2] module: expose imported namespaces via sysfs Nicholas Sielicki
2026-03-07 9:00 ` [PATCH v2 1/2] " Nicholas Sielicki
2026-03-07 9:30 ` Peter Zijlstra [this message]
2026-03-09 11:15 ` Matthias Männich
2026-03-07 9:00 ` [PATCH v2 2/2] docs: symbol-namespaces: mention sysfs attribute Nicholas Sielicki
2026-03-20 17:45 ` [PATCH v2 0/2] module: expose imported namespaces via sysfs Sami Tolvanen
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=20260307093006.GU606826@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=atomlin@atomlin.com \
--cc=corbet@lwn.net \
--cc=da.gomez@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@opensource.nslick.com \
--cc=maennich@google.com \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rdunlap@infradead.org \
--cc=samitolvanen@google.com \
--cc=skhan@linuxfoundation.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