patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: Somnath Kotur <somnath.kotur@broadcom.com>,
	Steeven Li <steeven.li@broadcom.com>,  dpdk-dev <dev@dpdk.org>,
	dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/bnxt: fix null termination of receive mbuf chain
Date: Sun, 24 Jan 2021 08:32:28 -0800	[thread overview]
Message-ID: <CACZ4nhsM55ZUXpaNFL88e1rpYx2vD07rjKEp_yGhueAhEaXqiQ@mail.gmail.com> (raw)
In-Reply-To: <20210122214900.10430-1-lance.richardson@broadcom.com>

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

On Fri, Jan 22, 2021 at 1:49 PM Lance Richardson
<lance.richardson@broadcom.com> wrote:
>
> The last mbuf in a multi-segment packet needs to be
> NULL-terminated.
>
> Fixes: 0958d8b6435d ("net/bnxt: support LRO")
> Cc: stable@dpdk.org
> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
> Reviewed-by: Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>
Patch applied to dpdk-next-net-brcm.

> ---
>  drivers/net/bnxt/bnxt_rxr.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/bnxt/bnxt_rxr.c b/drivers/net/bnxt/bnxt_rxr.c
> index 969cae19fc..c34a8905e7 100644
> --- a/drivers/net/bnxt/bnxt_rxr.c
> +++ b/drivers/net/bnxt/bnxt_rxr.c
> @@ -325,6 +325,7 @@ static int bnxt_rx_pages(struct bnxt_rx_queue *rxq,
>                  */
>                 rte_bitmap_set(rxr->ag_bitmap, ag_cons);
>         }
> +       last->next = NULL;
>         bnxt_prod_ag_mbuf(rxq);
>         return 0;
>  }
> --
> 2.25.1
>

      reply	other threads:[~2021-01-24 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 21:49 Lance Richardson
2021-01-24 16:32 ` 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=CACZ4nhsM55ZUXpaNFL88e1rpYx2vD07rjKEp_yGhueAhEaXqiQ@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=lance.richardson@broadcom.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=steeven.li@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 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).