netdev - Re: [PATCH rdma-next 0/9] RDMA/bnxt_re: Driver Debug Enhancements

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: <20250223133456.GA53094@unreal>
Date: Sun, 23 Feb 2025 15:34:56 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Selvin Xavier <selvin.xavier@...adcom.com>
Cc: jgg@...pe.ca, linux-rdma@...r.kernel.org,
	andrew.gospodarek@...adcom.com, kalesh-anakkur.purayil@...adcom.com,
	netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
	kuba@...nel.org, abeni@...hat.com, horms@...nel.org,
	michael.chan@...adcom.com
Subject: Re: [PATCH rdma-next 0/9] RDMA/bnxt_re: Driver Debug Enhancements

On Thu, Feb 20, 2025 at 10:34:47AM -0800, Selvin Xavier wrote:
> For debugging issues in the field, we need to track some of
> the resources destroyed in the past. This is primarily required
> for tracking certain QPs that encountered errors, leading to
> application exits. A framework has been implemented to
> save this information and retrieve it during coredump collection.
> 
> The Broadcom bnxt L2 driver supports collecting driver dumps
> using the ethtool -w option. This feature now also supports
> collecting coredump information from the bnxt_re auxiliary driver.
> Two new callbacks have been implemented to exchange dump
> information supported by the auxbus bnxt_re driver.
> 
> The bnxt_re driver caches certain hardware information before
> resources are destroyed in the HW.

Unfortunately, no. The idea that you will cache kernel objects and they
live beyond their HW counterpart doesn't fit RDMA object model.

I'm aware that you are not keeping objects itself, but their shadow
copy. So if you want, your FW can store these failed objects and you
will retrieve them through existing netdev side (ethtool -w ...).

Thanks