From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 734] memif driver crashes when there's different N of TX and RX queues
Date: Mon, 14 Jun 2021 15:49:42 +0000 [thread overview]
Message-ID: <bug-734-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=734
Bug ID: 734
Summary: memif driver crashes when there's different N of TX
and RX queues
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: ivan4th@gmail.com
Target Milestone: ---
There's a bug in memif_stats_get() function due to confusion between C2S
(client->server) and S2C (server->client) rings, causing a crash if there's a
different number of RX and TX queues. Fixed in downstream DPDK version in Cisco
TRex: https://github.com/cisco-system-traffic-generator/trex-core/pull/728
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-06-14 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 15:49 bugzilla [this message]
2022-10-10 10:40 ` 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-734-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).