From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Cian Ferriter <cian.ferriter@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org, rchibois@gmail.com
Subject: Re: [dpdk-stable] [PATCH] net/pcap: fix possible crash on exit for infinite Rx
Date: Mon, 12 Oct 2020 18:08:53 +0100 [thread overview]
Message-ID: <ff4ec94c-d103-1d4b-b1a2-cbe223d00860@intel.com> (raw)
In-Reply-To: <20201009161649.1365261-1-ferruh.yigit@intel.com>
On 10/9/2020 5:16 PM, Ferruh Yigit wrote:
> If the infinite Rx argument ('infinite_rx') is provided a ring is
> allocated and filled in the '.rx_queue_setup' dev_ops.
> Later this ring freed in the '.dev_close' dev_ops.
>
> If the 'infinite_rx' provided and '.dev_close' called before
> '.rx_queue_setup', the ring will be NULL and trying to empty/free it
> will cause a crash.
>
> This is fixed by adding ring NULL check before trying to empty/free it.
>
> Bugzilla ID: 548
> Fixes: a3f5252e5cbd ("net/pcap: enable infinitely Rx a pcap file")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-10-12 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 16:16 Ferruh Yigit
2020-10-12 17:08 ` Ferruh Yigit [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=ff4ec94c-d103-1d4b-b1a2-cbe223d00860@intel.com \
--to=ferruh.yigit@intel.com \
--cc=cian.ferriter@intel.com \
--cc=dev@dpdk.org \
--cc=rchibois@gmail.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).