From: Luca Boccassi <bluca@debian.org>
To: Somnath Kotur <somnath.kotur@broadcom.com>, stable@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-stable] [PATCH 20.11] net/bnxt: detect bad opaque in Rx completion
Date: Fri, 16 Jul 2021 12:08:41 +0100 [thread overview]
Message-ID: <31ef0f72260a7da4dcb6acc0cebeb057523e9c58.camel@debian.org> (raw)
In-Reply-To: <20210716062911.15394-1-somnath.kotur@broadcom.com>
On Fri, 2021-07-16 at 11:59 +0530, Somnath Kotur wrote:
> [ upstream commit 03c8f2fe111c2b4c4fddc960dc82253ac7e6c5c5 ]
>
> There is a rare hardware bug that can cause a bad opaque value in the RX
> or TPA start completion. When this happens, the hardware may have used the
> same buffer twice for 2 Rx packets. In addition, the driver might also
> crash later using the bad opaque as an index into the ring.
>
> The Rx opaque value is predictable and is always monotonically increasing.
> The workaround is to keep track of the expected next opaque value and
> compare it with the one returned by hardware during RX and TPA start
> completions. If they miscompare, log it, discard the completion,
> schedule a ring reset and move on to the next one.
>
> Fixes: 0958d8b6435d ("net/bnxt: support LRO")
>
> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> ---
> drivers/net/bnxt/bnxt_hwrm.c | 19 +++++++
> drivers/net/bnxt/bnxt_hwrm.h | 1 +
> drivers/net/bnxt/bnxt_rxq.h | 1 +
> drivers/net/bnxt/bnxt_rxr.c | 99 +++++++++++++++++++++++++++++++++++-
> drivers/net/bnxt/bnxt_rxr.h | 1 +
> 5 files changed, 119 insertions(+), 2 deletions(-)
Thanks, applied and pushed.
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2021-07-16 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 6:29 Somnath Kotur
2021-07-16 11:08 ` Luca Boccassi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31ef0f72260a7da4dcb6acc0cebeb057523e9c58.camel@debian.org \
--to=bluca@debian.org \
--cc=ajit.khaparde@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).