From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 932] tap stop fails because of 'tap_lsc_intr_handle_set()' failure
Date: Tue, 01 Feb 2022 17:04:51 +0000 [thread overview]
Message-ID: <bug-932-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=932
Bug ID: 932
Summary: tap stop fails because of 'tap_lsc_intr_handle_set()'
failure
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: ferruh.yigit@intel.com
Target Milestone: ---
Reproduced with testpmd with following command flow:
./build/app/dpdk-testpmd --vdev net_tap0 --vdev net_tap1 --vdev net_tap2 -- -i
> start tx_first
> stop
> quit
Log:
Stopping port 2...
Stopping ports...
tap_lsc_intr_handle_set(): intr callback unregister failed: -2
free(): invalid pointer
Aborted (core dumped)
Quick debug shows that in 'pmd->intr_handle->fd' is '0' may be reason of the
error.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-02-01 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 17:04 bugzilla [this message]
2022-02-02 17:30 ` kumaraparameshwaran rathinavel
2024-02-28 0:40 ` [DPDK/ethdev Bug " bugzilla
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=bug-932-3@http.bugs.dpdk.org/ \
--to=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).