netdev - Re: [PATCH net-next 2/2] bnx2x: Invalidate fastpath HSI version for VFs

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: <YXhfhll786/fGuur@kroah.com>
Date:   Tue, 26 Oct 2021 22:05:26 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Manish Chopra <manishc@...vell.com>
Cc:     kuba@...nel.org, netdev@...r.kernel.org, stable@...r.kernel.org,
        aelior@...vell.com, skalluru@...vell.com, malin1024@...il.com,
        smalin@...vell.com, okulkarni@...vell.com, njavali@...vell.com,
        GR-everest-linux-l2@...vell.com
Subject: Re: [PATCH net-next 2/2] bnx2x: Invalidate fastpath HSI version for
 VFs

On Tue, Oct 26, 2021 at 12:37:17PM -0700, Manish Chopra wrote:
> Commit 0a6890b9b4df ("bnx2x: Utilize FW 7.13.15.0.")
> added validation for fastpath HSI versions for different
> client init which was not meant for SR-IOV VF clients, which
> resulted in firmware asserts when running VF clients with
> different fastpath HSI version.
> 
> This patch along with the new firmware support in patch #1
> fixes this behavior in order to not validate fastpath HSI
> version for the VFs.
> 
> Fixes: 0a6890b9b4df ("bnx2x: Utilize FW 7.13.15.0.")
> Signed-off-by: Manish Chopra <manishc@...vell.com>
> Signed-off-by: Ariel Elior <aelior@...vell.com>
> Signed-off-by: Omkar Kulkarni <okulkarni@...vell.com>
> Signed-off-by: Shai Malin <smalin@...vell.com>


<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>