From: Leon Romanovsky <leon@kernel.org>
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew+netdev@lunn.ch,
pavan.chebbi@broadcom.com, andrew.gospodarek@broadcom.com,
Srijit Bose <srijit.bose@broadcom.com>,
Ray Jui <ray.jui@broadcom.com>
Subject: Re: [PATCH net] bnxt_en: Fix potential data corruption with HW GRO/LRO
Date: Thu, 25 Dec 2025 14:52:29 +0200 [thread overview]
Message-ID: <20251225125229.GL11869@unreal> (raw)
In-Reply-To: <20251224191116.3526999-1-michael.chan@broadcom.com>
On Wed, Dec 24, 2025 at 11:11:16AM -0800, Michael Chan wrote:
> From: Srijit Bose <srijit.bose@broadcom.com>
>
> Fix the max number of bits passed to find_first_zero_bit() in
> bnxt_alloc_agg_idx(). We were incorrectly passing the number of
> long words. find_first_zero_bit() may fail to find a zero bit and
> cause a wrong ID to be used. If the wrong ID is already in use, this
> can cause data corruption. Sometimes an error like this can also be
> seen:
>
> bnxt_en 0000:83:00.0 enp131s0np0: TPA end agg_buf 2 != expected agg_bufs 1
>
> Fix it by passing the correct number of bits MAX_TPA_P5. Add a sanity
> BUG_ON() check if find_first_zero_bit() fails. It should never happen.
Things that should never occur are flagged with WARN_ON(), not BUG_ON().
Using BUG_ON() would unnecessarily crash the system just because something
unexpected happened in the networking driver.
Thanks
>
> Fixes: ec4d8e7cf024 ("bnxt_en: Add TPA ID mapping logic for 57500 chips.")
> Reviewed-by: Ray Jui <ray.jui@broadcom.com>
> Signed-off-by: Srijit Bose <srijit.bose@broadcom.com>
> Signed-off-by: Michael Chan <michael.chan@broadcom.com>
> ---
> drivers/net/ethernet/broadcom/bnxt/bnxt.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> index d17d0ea89c36..6704cbbc1b24 100644
> --- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> @@ -1482,9 +1482,10 @@ static u16 bnxt_alloc_agg_idx(struct bnxt_rx_ring_info *rxr, u16 agg_id)
> struct bnxt_tpa_idx_map *map = rxr->rx_tpa_idx_map;
> u16 idx = agg_id & MAX_TPA_P5_MASK;
>
> - if (test_bit(idx, map->agg_idx_bmap))
> - idx = find_first_zero_bit(map->agg_idx_bmap,
> - BNXT_AGG_IDX_BMAP_SIZE);
> + if (test_bit(idx, map->agg_idx_bmap)) {
> + idx = find_first_zero_bit(map->agg_idx_bmap, MAX_TPA_P5);
> + BUG_ON(idx >= MAX_TPA_P5);
> + }
> __set_bit(idx, map->agg_idx_bmap);
> map->agg_id_tbl[agg_id] = idx;
> return idx;
> --
> 2.51.0
>
>
prev parent reply other threads:[~2025-12-25 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 19:11 [PATCH net] bnxt_en: Fix potential data corruption with HW GRO/LRO Michael Chan
2025-12-25 9:34 ` Vadim Fedorenko
2025-12-25 12:52 ` Leon Romanovsky [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=20251225125229.GL11869@unreal \
--to=leon@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=ray.jui@broadcom.com \
--cc=srijit.bose@broadcom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.