patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix mbufs replenishment check for zipped CQEs
Date: Tue, 17 Aug 2021 09:48:16 +0000	[thread overview]
Message-ID: <DM4PR12MB50540FD9FF98FA10F2CD7C3ACFFE9@DM4PR12MB5054.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210804062316.1688851-1-akozyrev@nvidia.com>

Hi,
> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Wednesday, August 4, 2021 9:23 AM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Subject: [PATCH] net/mlx5: fix mbufs replenishment check for zipped CQEs
> 
> A core dump is being generated with the following call stack:
> 0 _mm256_storeu_si256 (__A=..., __P=0x80)
> 1 rte_mov32 (src=0x2299c9140 "", dst=0x80)
> 2 rte_memcpy_aligned (n=60, src=0x2299c9140, dst=0x80)
> 3 rte_memcpy (n=60, src=0x2299c9140, dst=0x80)
> 4 mprq_buf_to_pkt (strd_cnt=1, strd_idx=0, buf=0x2299c8a00, len=60,
> pkt=0x18345f0c0, rxq=0x18345ef40)
> 5 rxq_copy_mprq_mbuf_v (rxq=0x18345ef40, pkts=0x7f76e0ff6d18,
> pkts_n=5)
> 6 rxq_burst_mprq_v (rxq=0x18345ef40, pkts=0x7f76e0ff6d18, pkts_n=46,
> err=0x7f76e0ff6a28, no_cq=0x7f76e0ff6a27)
> 7 mlx5_rx_burst_mprq_vec (dpdk_rxq=0x18345ef40, pkts=0x7f76e0ff6a88,
> pkts_n=128)
> 8 rte_eth_rx_burst (nb_pkts=128, rx_pkts=0x7f76e0ff6a88,
> queue_id=<optimized out>, port_id=<optimized out>)
> 
> This crash is caused by an attempt to copy previously uncompressed CQEs
> into non-allocated mbufs. There is a check to make sure we only use
> allocated mbufs in the rxq_burst_mprq_v() function, but it is done only
> before the main processing loop. Leftovers of compressed CQEs session are
> handled before that loop and may lead to the mbufs overflow as seen.
> 
> Move the check for replenished mbufs up to protect uncompressed CQEs
> session leftovers from accessing non-allocated mbufs after the
> mlx5_rx_mprq_replenish_bulk_mbuf() function is invoked.
> 
> Bugzilla ID: 746
> Fixes: 0f20acbf5e ("net/mlx5: implement vectorized MPRQ burst")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh


      reply	other threads:[~2021-08-17  9:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04  6:23 Alexander Kozyrev
2021-08-17  9:48 ` Raslan Darawsheh [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=DM4PR12MB50540FD9FF98FA10F2CD7C3ACFFE9@DM4PR12MB5054.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=akozyrev@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@nvidia.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).