netdev - Re: [PATCH v5 0/8] Introduce fwctl subystem

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <2025031840-phrasing-rink-c7bb@gregkh>
Date: Tue, 18 Mar 2025 14:20:45 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "Keller, Jacob E" <jacob.e.keller@...el.com>
Cc: David Ahern <dsahern@...nel.org>, Jason Gunthorpe <jgg@...dia.com>,
	"Nelson, Shannon" <shannon.nelson@....com>,
	Leon Romanovsky <leon@...nel.org>, Jiri Pirko <jiri@...nulli.us>,
	Jakub Kicinski <kuba@...nel.org>,
	Andy Gospodarek <andrew.gospodarek@...adcom.com>,
	Aron Silverton <aron.silverton@...cle.com>,
	"Williams, Dan J" <dan.j.williams@...el.com>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	"Jiang, Dave" <dave.jiang@...el.com>,
	Christoph Hellwig <hch@...radead.org>,
	Itay Avraham <itayavr@...dia.com>, Jiri Pirko <jiri@...dia.com>,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	Leonid Bloch <lbloch@...dia.com>,
	"linux-cxl@...r.kernel.org" <linux-cxl@...r.kernel.org>,
	"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Saeed Mahameed <saeedm@...dia.com>,
	"Sinyuk, Konstantin" <konstantin.sinyuk@...el.com>
Subject: Re: [PATCH v5 0/8] Introduce fwctl subystem

On Mon, Mar 17, 2025 at 08:33:04PM +0000, Keller, Jacob E wrote:
> 
> 
> > -----Original Message-----
> > From: David Ahern <dsahern@...nel.org>
> > Sent: Monday, March 17, 2025 12:01 PM
> > To: Jason Gunthorpe <jgg@...dia.com>; Keller, Jacob E
> > <jacob.e.keller@...el.com>
> > Cc: Nelson, Shannon <shannon.nelson@....com>; Leon Romanovsky
> > <leon@...nel.org>; Jiri Pirko <jiri@...nulli.us>; Jakub Kicinski
> > <kuba@...nel.org>; Greg Kroah-Hartman <gregkh@...uxfoundation.org>; Andy
> > Gospodarek <andrew.gospodarek@...adcom.com>; Aron Silverton
> > <aron.silverton@...cle.com>; Williams, Dan J <dan.j.williams@...el.com>; Daniel
> > Vetter <daniel.vetter@...ll.ch>; Jiang, Dave <dave.jiang@...el.com>; Christoph
> > Hellwig <hch@...radead.org>; Itay Avraham <itayavr@...dia.com>; Jiri Pirko
> > <jiri@...dia.com>; Jonathan Cameron <Jonathan.Cameron@...wei.com>;
> > Leonid Bloch <lbloch@...dia.com>; linux-cxl@...r.kernel.org; linux-
> > rdma@...r.kernel.org; netdev@...r.kernel.org; Saeed Mahameed
> > <saeedm@...dia.com>; Sinyuk, Konstantin <konstantin.sinyuk@...el.com>
> > Subject: Re: [PATCH v5 0/8] Introduce fwctl subystem
> > 
> > On 3/17/25 1:33 PM, Jason Gunthorpe wrote:
> > > On Fri, Mar 14, 2025 at 11:09:47AM -0700, Jacob Keller wrote:
> > >
> > >> I'd throw my hat in for drivers/core as well, I think it makes the most
> > >> sense and is the most subsystem neutral name. Hopefully any issue with
> > >> tooling can be solved relatively easily.
> > >
> > > Given Greg's point about core dump files sometimes being in .gitignore
> > > maybe "shared_core", or something along that path is a better name?
> > >
> > 
> > Not seeing the conflict on drivers/core:
> > 
> > $ find . -name .gitignore | xargs grep core
> > ./tools/testing/selftests/powerpc/ptrace/.gitignore:core-pkey
> > ./tools/testing/selftests/cgroup/.gitignore:test_core
> > ./tools/testing/selftests/mincore/.gitignore:mincore_selftest
> > ./arch/mips/crypto/.gitignore:poly1305-core.S
> > ./arch/arm/crypto/.gitignore:aesbs-core.S
> > ./arch/arm/crypto/.gitignore:sha256-core.S
> > ./arch/arm/crypto/.gitignore:sha512-core.S
> > ./arch/arm/crypto/.gitignore:poly1305-core.S
> > ./arch/arm64/crypto/.gitignore:sha256-core.S
> > ./arch/arm64/crypto/.gitignore:sha512-core.S
> > ./arch/arm64/crypto/.gitignore:poly1305-core.S
> 
> I would guess its people putting core in their own ignore lists, not necessarily what we commit to the kernel tree.

Yes, note, the issue came up in the 2.5.x kernel days, _WAY_ before we
had git, so this wasn't a git issue.  I'm all for "drivers/core/" but
note, that really looks like "the driver core" area of the kernel, so
maybe pick a different name?

Maybe drivers/lib/ as this is common stuff for a variety of different
drivers?  I don't know, naming is hard, sorry.  I've been defaulting to
just using dutch words for projects these days as they don't seem to be
used much.  Hey, that might work here, drivers/kern/ perhaps?  Nah...

thanks,

greg k-h