[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdUgO83KksK59XEmF+EqXWHWBd1FLML0Ee1dQ7nOiGV2Eg@mail.gmail.com>
Date: Fri, 8 Nov 2024 09:08:30 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: Peter Zijlstra <peterz@...radead.org>, mcgrof@...nel.org, x86@...nel.org, hpa@...or.com,
petr.pavlu@...e.com, samitolvanen@...gle.com, da.gomez@...sung.com,
masahiroy@...nel.org, nathan@...nel.org, nicolas@...sle.eu,
linux-kernel@...r.kernel.org, linux-modules@...r.kernel.org,
linux-kbuild@...r.kernel.org, gregkh@...uxfoundation.org
Subject: Re: [RFC] module: Strict per-modname namespaces
On Thu, Nov 7, 2024 at 6:39 AM Christoph Hellwig <hch@...radead.org> wrote:
> On Wed, Nov 06, 2024 at 08:02:40PM +0100, Peter Zijlstra wrote:
> > It reserves and disallows imports on any "MODULE_${name}" namespace,
> > while it implicitly adds the same namespace to every module.
>
> Ah nice. This is pretty similar to what I want and had badly prototyped
> a while ago.
>
> > This allows exports targeted at specific modules and no others -- one
> > random example included. I've hated the various kvm exports we've had
> > for a while, and strictly limiting them to the kvm module helps
> > alleviate some abuse potential.
>
> And this was one of the targets on my list. Specific kunits tests
> would be another category.
Indeed. E.g. making the scsi_lib KUnit tests modular would require
exporting an internal symbol[1], which the SCSI maintainers don't like.
[1] "[PATCH] scsi: core: Make scsi_lib KUnit tests modular for real"
https://lore.kernel.org/all/48ca5e827ca420bbdbabb1643e2179dc95c9e0b7.1710849638.git.geert@linux-m68k.org/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists