patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dev@dpdk.org
Cc: Kishore Padmanabha <kishore.padmanabha@broadcom.com>,
	stable@dpdk.org,  Jay Ding <jay.ding@broadcom.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] net/bnxt: fix segmentation fault
Date: Wed, 20 Nov 2024 13:15:42 -0800	[thread overview]
Message-ID: <CACZ4nhuv-RjynrA9hvn020W6XVP3+rvaoQtoYc32xsCoQsOHKw@mail.gmail.com> (raw)
In-Reply-To: <20241120170058.18742-1-ajit.khaparde@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

On Wed, Nov 20, 2024 at 9:01 AM Ajit Khaparde
<ajit.khaparde@broadcom.com> wrote:
>
> From: Kishore Padmanabha <kishore.padmanabha@broadcom.com>
>
> The mbuf offload flags were not reset before the flags were
> populated with the received packet details. This causes certain
> applications to act differently on the offload flags. That can
> cause application to assert at many locations.
>
> Fixes: 65d2b0557ba3 ("net/bnxt: support Rx completion v3")
> Cc: stable@dpdk.org
>
> Signed-off-by: Kishore Padmanabha <kishore.padmanabha@broadcom.com>
> Reviewed-by: Jay Ding <jay.ding@broadcom.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>

Fixed up a typo and merged into dpdk-next-net-brcm. Thanks


> ---
>  drivers/net/bnxt/bnxt_rxr.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/bnxt/bnxt_rxr.h b/drivers/net/bnxt/bnxt_rxr.h
> index 5e5496964f..7357ca4427 100644
> --- a/drivers/net/bnxt/bnxt_rxr.h
> +++ b/drivers/net/bnxt/bnxt_rxr.h
> @@ -535,6 +535,6 @@ bnxt_parse_csum_v3(struct rte_mbuf *mbuf, struct rx_pkt_cmpl_hi *rxcmp1)
>         uint16_t error_v2 = rte_le_to_cpu_16(v3_cmp->errors_v2);
>         uint32_t flags2 = rte_le_to_cpu_32(v3_cmp->flags2);
>
> -       mbuf->ol_flags |= bnxt_parse_csum_fields_v3(flags2, error_v2);
> +       mbuf->ol_flags = bnxt_parse_csum_fields_v3(flags2, error_v2);
>  }
>  #endif /*  _BNXT_RXR_H_ */
> --
> 2.39.5 (Apple Git-154)
>

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]

      parent reply	other threads:[~2024-11-20 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 17:00 Ajit Khaparde
2024-11-20 21:14 ` Patrick Robb
2024-11-20 21:15 ` Ajit Khaparde [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=CACZ4nhuv-RjynrA9hvn020W6XVP3+rvaoQtoYc32xsCoQsOHKw@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=jay.ding@broadcom.com \
    --cc=kishore.padmanabha@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).