patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Somnath Kotur <somnath.kotur@broadcom.com>,
	dev@dpdk.org, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/bnxt: fix uninitialized variable access
Date: Mon, 5 Nov 2018 09:38:13 -0800	[thread overview]
Message-ID: <CACZ4nhuAg5ucbHUny+MgRpSZ=HScbKURw=YXqWAT3fgxAioXEg@mail.gmail.com> (raw)
In-Reply-To: <20181028043542.87350-1-ferruh.yigit@intel.com>

On Sat, Oct 27, 2018 at 8:36 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> ag_cons is used uninitialized, it is used when DEBUG enabled, remove
> debug code.
>
> Fixes: 0958d8b6435d ("net/bnxt: support LRO")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>

We have not enabled this for debug for a while now.
We can remove this. Thanks



> ---
>  drivers/net/bnxt/bnxt_rxr.c | 24 ------------------------
>  1 file changed, 24 deletions(-)
>
> diff --git a/drivers/net/bnxt/bnxt_rxr.c b/drivers/net/bnxt/bnxt_rxr.c
> index c7bc88481..1bfc63d93 100644
> --- a/drivers/net/bnxt/bnxt_rxr.c
> +++ b/drivers/net/bnxt/bnxt_rxr.c
> @@ -102,25 +102,6 @@ static inline void bnxt_reuse_rx_mbuf(struct
> bnxt_rx_ring_info *rxr,
>         rxr->rx_prod = prod;
>  }
>
> -#ifdef BNXT_DEBUG
> -static void bnxt_reuse_ag_mbuf(struct bnxt_rx_ring_info *rxr, uint16_t
> cons,
> -                              struct rte_mbuf *mbuf)
> -{
> -       uint16_t prod = rxr->ag_prod;
> -       struct bnxt_sw_rx_bd *prod_rx_buf;
> -       struct rx_prod_pkt_bd *prod_bd, *cons_bd;
> -
> -       prod_rx_buf = &rxr->ag_buf_ring[prod];
> -
> -       prod_rx_buf->mbuf = mbuf;
> -
> -       prod_bd = &rxr->ag_desc_ring[prod];
> -       cons_bd = &rxr->ag_desc_ring[cons];
> -
> -       prod_bd->address = cons_bd->addr;
> -}
> -#endif
> -
>  static inline
>  struct rte_mbuf *bnxt_consume_rx_buf(struct bnxt_rx_ring_info *rxr,
>                                      uint16_t cons)
> @@ -377,9 +358,6 @@ static int bnxt_rx_pkt(struct rte_mbuf **rx_pkt,
>         uint32_t tmp_raw_cons = *raw_cons;
>         uint16_t cons, prod, cp_cons =
>             RING_CMP(cpr->cp_ring_struct, tmp_raw_cons);
> -#ifdef BNXT_DEBUG
> -       uint16_t ag_cons;
> -#endif
>         struct rte_mbuf *mbuf;
>         int rc = 0;
>         uint8_t agg_buf = 0;
> @@ -482,8 +460,6 @@ static int bnxt_rx_pkt(struct rte_mbuf **rx_pkt,
>         if (rxcmp1->errors_v2 & RX_CMP_L2_ERRORS) {
>                 /* Re-install the mbuf back to the rx ring */
>                 bnxt_reuse_rx_mbuf(rxr, cons, mbuf);
> -               if (agg_buf)
> -                       bnxt_reuse_ag_mbuf(rxr, ag_cons, mbuf);
>
>                 rc = -EIO;
>                 goto next_rx;
> --
> 2.17.2
>
>

  reply	other threads:[~2018-11-05 17:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28  4:35 Ferruh Yigit
2018-11-05 17:38 ` Ajit Khaparde [this message]
2018-11-05 17:56   ` Ferruh Yigit

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='CACZ4nhuAg5ucbHUny+MgRpSZ=HScbKURw=YXqWAT3fgxAioXEg@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).