netdev - Re: [PATCH net] bnxt_en: Fix RX consumer index logic in the error path.

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: <161940060923.7794.16850329658399665292.git-patchwork-notify@kernel.org>
Date:   Mon, 26 Apr 2021 01:30:09 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Michael Chan <michael.chan@...adcom.com>
Cc:     davem@...emloft.net, netdev@...r.kernel.org, kuba@...nel.org,
        gospo@...adcom.com
Subject: Re: [PATCH net] bnxt_en: Fix RX consumer index logic in the error path.

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Fri, 23 Apr 2021 18:13:19 -0400 you wrote:
> In bnxt_rx_pkt(), the RX buffers are expected to complete in order.
> If the RX consumer index indicates an out of order buffer completion,
> it means we are hitting a hardware bug and the driver will abort all
> remaining RX packets and reset the RX ring.  The RX consumer index
> that we pass to bnxt_discard_rx() is not correct.  We should be
> passing the current index (tmp_raw_cons) instead of the old index
> (raw_cons).  This bug can cause us to be at the wrong index when
> trying to abort the next RX packet.  It can crash like this:
> 
> [...]

Here is the summary with links:
  - [net] bnxt_en: Fix RX consumer index logic in the error path.
    https://git.kernel.org/netdev/net/c/bbd6f0a94813

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html