netdev - Re: [PATCH v10 0/2] bnx2x: Fix error recovering in switch configuration

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]

Date: Wed, 14 Feb 2024 12:48:23 -0800
From: Jacob Keller <jacob.e.keller@...el.com>
To: Thinh Tran <thinhtr@...ux.vnet.ibm.com>, <kuba@...nel.org>
CC: <netdev@...r.kernel.org>, <davem@...emloft.net>, <manishc@...vell.com>,
	<pabeni@...hat.com>, <skalluru@...vell.com>, <simon.horman@...igine.com>,
	<edumazet@...gle.com>, <VENKATA.SAI.DUGGI@....com>, <drc@...ux.vnet.ibm.com>,
	<abdhalee@...ibm.com>
Subject: Re: [PATCH v10 0/2] bnx2x: Fix error recovering in switch
 configuration



On 2/13/2024 10:32 AM, Thinh Tran wrote:
> Please refer to the initial cover letter
> https://lore.kernel.org/all/20230818161443.708785-1-thinhtr@linux.vnet.ibm.com
> 
> In series Version 6, the patch
>    [v6,1/4] bnx2x: new flag for tracking HW resource
> was successfully made it to the mainline kernel
> https://github.com/torvalds/linux/commit/bf23ffc8a9a777dfdeb04232e0946b803adbb6a9
> but the rest of the patches did not.
> 
> The following patch has been excluded from this series:
>     net/bnx2x: prevent excessive debug information during a TX timeout
> based on concerns raised by some developers that it might omit valuable
> debugging details as in some other scenarios may cause the TX timeout.
> 
> 
> v9: adding "Fixes:" tag to commit messages for patch
>     net/bnx2x: Prevent access to a freed page in page_pool
> 
> v8: adding stack trace to commit messages for patch
>     net/bnx2x: Prevent access to a freed page in page_pool
> 
> v7: resubmitting patches.
> 

The subject didn't clearly identify net-next or net... but the contents
of the series seem to be one bug fix which would make sense to go to net
(unless the bug itself isn't in net yet?) and one refactor that doesn't
seem reasonable to go to net..