From: Stephen Hemminger <stephen@networkplumber.org>
To: bugzilla@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [Bug 382] rte_eth: rx/tx callbacks invoked without lock protection
Date: Thu, 9 Jan 2020 08:10:41 -0800 [thread overview]
Message-ID: <20200109081041.2c05f312@hermes.lan> (raw)
In-Reply-To: <bug-382-3@http.bugs.dpdk.org/>
On Thu, 09 Jan 2020 07:52:34 +0000
bugzilla@dpdk.org wrote:
> https://bugs.dpdk.org/show_bug.cgi?id=382
>
> Bug ID: 382
> Summary: rte_eth: rx/tx callbacks invoked without lock
> protection
> Product: DPDK
> Version: 18.11
> Hardware: All
> OS: All
> Status: UNCONFIRMED
> Severity: normal
> Priority: Normal
> Component: ethdev
> Assignee: dev@dpdk.org
> Reporter: zhongdahulinfan@163.com
> Target Milestone: ---
>
> Hi, all
> I launch my DPDK app, and then use dpdk-pdump to capture wire packets. When
> I stop dpdk-pdump with ctrl+c, my DPDK app crash. Here is the coredump
> backtrace:
>
> ```
dpdk-pdump needs a signal handler to catch control-c and unregister its
callback.
prev parent reply other threads:[~2020-01-09 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 7:52 bugzilla
2020-01-09 16:10 ` Stephen Hemminger [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=20200109081041.2c05f312@hermes.lan \
--to=stephen@networkplumber.org \
--cc=bugzilla@dpdk.org \
--cc=dev@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).