netdev - Re: [PATCH v4 10/10] bnxt: Create an auxiliary device for fwctl

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: <CACDg6nX-W7hzDUFMDmEtaZGUJu5dnSzcZpTXpn__O1kEu0ddRQ@mail.gmail.com>
Date: Fri, 7 Feb 2025 22:24:11 -0500
From: Andy Gospodarek <andrew.gospodarek@...adcom.com>
To: Jason Gunthorpe <jgg@...dia.com>
Cc: Jakub Kicinski <kuba@...nel.org>, Saeed Mahameed <saeedm@...dia.com>, 
	Aron Silverton <aron.silverton@...cle.com>, Dan Williams <dan.j.williams@...el.com>, 
	Daniel Vetter <daniel.vetter@...ll.ch>, Dave Jiang <dave.jiang@...el.com>, 
	David Ahern <dsahern@...nel.org>, Andy Gospodarek <gospo@...adcom.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>, 
	Leon Romanovsky <leonro@...dia.com>, linux-cxl@...r.kernel.org, linux-rdma@...r.kernel.org, 
	netdev@...r.kernel.org, "Nelson, Shannon" <shannon.nelson@....com>, 
	Michael Chan <michael.chan@...adcom.com>
Subject: Re: [PATCH v4 10/10] bnxt: Create an auxiliary device for fwctl_bnxt

On Fri, Feb 7, 2025 at 8:16 PM Jason Gunthorpe <jgg@...dia.com> wrote:
>
> On Fri, Feb 07, 2025 at 01:51:11PM -0800, Jakub Kicinski wrote:
>
> > But if you agree the netdev doesn't need it seems like a fairly
> > straightforward way to unblock your progress.
>
> I'm trying to understand what you are suggesting here.
>
> We have many scenarios where mlx5_core spawns all kinds of different
> devices, including recovery cases where there is no networking at all
> and only fwctl. So we can't just discard the aux dev or mlx5_core
> triggered setup without breaking scenarios.
>
> However, you seem to be suggesting that netdev-only configurations (ie
> netdev loaded but no rdma loaded) should disable fwctl. Is that the
> case? All else would remain the same. It is very ugly but I could see
> a technical path to do it, and would consider it if that brings peace.
>

We can probably live with that as well if it's required to keep fwctl
in an RDMA driver and out of pure netdevs.