[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241112195226.GT22801@noisy.programming.kicks-ass.net>
Date: Tue, 12 Nov 2024 20:52:26 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Sean Christopherson <seanjc@...gle.com>
Cc: 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,
hch@...radead.org, gregkh@...uxfoundation.org
Subject: Re: [RFC][PATCH 0/8] module: Strict per-modname namespaces
On Tue, Nov 12, 2024 at 09:56:20AM -0800, Sean Christopherson wrote:
> This likely needs to be addressed in whatever chunk of code is enforcing the
> namespaces. The s/-/_ behavior (and vice versa!) is *very* baked into the kernel
> at this point, e.g. parameqn() will happily parse dashes or underscores for every
> kernel parameter. As horrific as it is, I think the module namespace needs to do
> the same, i.e. treat dashes and underscores as one and the same.
Right, I'll add a s/-/_/g on both ends of the strcmp or somesuch.
Powered by blists - more mailing lists