From: kumaraparameshwaran rathinavel <kumaraparamesh92@gmail.com>
To: bugzilla@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [Bug 932] tap stop fails because of 'tap_lsc_intr_handle_set()' failure
Date: Wed, 2 Feb 2022 23:00:08 +0530 [thread overview]
Message-ID: <CANxNyatdRuSq6JAU6w40MhP77EzZuNOaXrXmwtwPD_qjjK2euQ@mail.gmail.com> (raw)
In-Reply-To: <bug-932-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
On Tue, Feb 1, 2022, 10:34 PM <bugzilla@dpdk.org> wrote:
> 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.
> Ferruh, I think this because of the intr_vec, so there should be a way to
> differentiate if vec was used or not ? Or should we just assume that if the
> fd is 0 then intr_vec was installed. ?
--
> You are receiving this mail because:
> You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2201 bytes --]
next prev parent reply other threads:[~2022-02-02 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 17:04 bugzilla
2022-02-02 17:30 ` kumaraparameshwaran rathinavel [this message]
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=CANxNyatdRuSq6JAU6w40MhP77EzZuNOaXrXmwtwPD_qjjK2euQ@mail.gmail.com \
--to=kumaraparamesh92@gmail.com \
--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).