linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	 Luis Chamberlain <mcgrof@kernel.org>,
	Kees Cook <kees@kernel.org>, Jan Kara <jack@suse.cz>,
	 linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 06/15] fs,fork,exit: export symbols necessary for KUnit UAPI support
Date: Mon, 14 Jul 2025 10:12:56 +0200	[thread overview]
Message-ID: <20250714-fernhalten-holzkisten-d085d5802884@brauner> (raw)
In-Reply-To: <20250714073704-ad146959-da12-4451-be01-819aba61c917@linutronix.de>

On Mon, Jul 14, 2025 at 07:52:27AM +0200, Thomas Weißschuh wrote:
> (+Luis for the usermode helper discussion)
> 
> On Fri, Jul 11, 2025 at 04:44:23PM +0100, Al Viro wrote:
> > On Fri, Jul 11, 2025 at 12:35:59PM +0200, Thomas Weißschuh wrote:
> > > Hi Kees, Al, Christian and Honza,
> > > 
> > > On Thu, Jun 26, 2025 at 08:10:14AM +0200, Thomas Weißschuh wrote:
> > > > The KUnit UAPI infrastructure starts userspace processes.
> > > > As it should be able to be built as a module, export the necessary symbols.
> > 
> > What's wrong with kernel/umh.c?
> 
> It gets neutered by CONFIG_STATIC_USERMODEHELPER_PATH. That could be worked
> around be overriding sub_info->path, but it would be a hack.
> It does not allow to implement a custom wait routine to forward the process
> output to KUnit as implemented in kunit_uapi_forward_to_printk() [0].
> That may be solved by adding another thread, but that would also be hacky.
> 
> It would probably be possible to extend kernel/umh.c for my usecase but I
> didn't want bloat the core kernel code for my test-only functionality.
> 
> > > could you take a look at these new symbol exports?
> > 
> > > > +EXPORT_SYMBOL_GPL_FOR_MODULES(put_filesystem, "kunit-uapi");
> > 
> > What's that one for???
> 
> What are you referring to?
> 
> The macro EXPORT_SYMBOL_GPL_FOR_MODULES() will only export the symbol for one
> specific module. Personally I'm also fine with EXPORT_SYMBOL_GPL().

No, we're going to use the new restricted macros going forward that
limit exports to very specific modules. This is a good example. Though
it will be renamed to EXPORT_SYMBOL_FOR_MODULES() anyway.


  reply	other threads:[~2025-07-14  8:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26  6:10 [PATCH v4 00/15] kunit: Introduce UAPI testing framework Thomas Weißschuh
2025-06-26  6:10 ` [PATCH v4 06/15] fs,fork,exit: export symbols necessary for KUnit UAPI support Thomas Weißschuh
2025-07-11 10:35   ` Thomas Weißschuh
2025-07-11 15:44     ` Al Viro
2025-07-14  5:52       ` Thomas Weißschuh
2025-07-14  8:12         ` Christian Brauner [this message]
2025-07-16  5:30         ` Thomas Weißschuh
2025-07-16  6:21           ` Christoph Hellwig
2025-07-16  8:39             ` Thomas Weißschuh
2025-07-16 11:11               ` Christoph Hellwig
2025-07-16 11:33                 ` Thomas Weißschuh
2025-07-16 11:36                   ` Christoph Hellwig
2025-07-16 12:47                     ` Thomas Weißschuh
2025-07-16 12:57                       ` Christoph Hellwig
2025-06-26  6:10 ` [PATCH v4 12/15] kunit: Introduce UAPI testing framework Thomas Weißschuh
2025-06-26 18:11   ` Benjamin Berg
2025-06-27  4:20     ` Thomas Weißschuh
2025-06-27  6:58       ` Benjamin Berg
2025-06-27  8:27         ` Thomas Weißschuh
2025-07-07 18:18 ` [PATCH v4 00/15] " Jonathan Corbet
2025-07-08  5:51   ` Thomas Weißschuh

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=20250714-fernhalten-holzkisten-d085d5802884@brauner \
    --to=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=kees@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mcgrof@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    /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).