linux-kernel - Re: [RFC PATCH v3] nubus: Don't list slot resources by default

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20230404211618.GA26628@allandria.com>
Date:   Tue, 4 Apr 2023 14:16:18 -0700
From:   Brad Boyer <flar@...andria.com>
To:     Finn Thain <fthain@...ux-m68k.org>
Cc:     Geert Uytterhoeven <geert@...ux-m68k.org>,
        linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v3] nubus: Don't list slot resources by default

On Tue, Apr 04, 2023 at 08:50:59AM +1000, Finn Thain wrote:
> On Sun, 2 Apr 2023, Brad Boyer wrote:
> > Would it be better to give this option a name that indicates that it is 
> > for nubus only? These are effectively a global namespace. Other than 
> > this, I don't see any issues.
> 
> The name of the module here is "nubus", so this parameter is specified as 
> "nubus.populate_procfs" in the kernel parameters. Without the "nubus" it 
> doesn't work. I should probably add a comment about that.

OK. A comment would be good. Thank you for the clarification. It's been
a while since I needed to use anything like that myself. The code I
deal with on a regular basis is never built-in, so I missed how that
worked these days. Now that I looked at the headers, I see how that
works to add the prefix depending on the build type.

	Brad Boyer
	flar@...andria.com