From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 384] netvsc PMD crashes in secondary process in dev_info_get
Date: Fri, 10 Jan 2020 22:36:44 +0000 [thread overview]
Message-ID: <bug-384-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=384
Bug ID: 384
Summary: netvsc PMD crashes in secondary process in
dev_info_get
Product: DPDK
Version: 19.08
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Call rte_ethdev_dev_info_get in a secondary process will crash with netvsc PMD.
The data structure mapping for the vmbus is not mapped at same address.
It is crashing here because hv->vmbus is not the correct in secondary.
static void *hn_rndis_alloc(struct hn_data *hv, size_t size)
{
return rte_zmalloc_socket("RNDIS", size, PAGE_SIZE,
hv->vmbus->device.numa_node);
}
The numa_node is not needed for control messages.
But fixing that just exposes the next crash when sending the control message.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-01-10 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 22:36 bugzilla [this message]
2020-03-16 23:58 ` 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-384-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).