From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 862] Uninitialized value of devargs.bus_str for RTE_DEVARGS_KEY_CLASS case
Date: Thu, 28 Oct 2021 17:55:26 +0000 [thread overview]
Message-ID: <bug-862-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=862
Bug ID: 862
Summary: Uninitialized value of devargs.bus_str for
RTE_DEVARGS_KEY_CLASS case
Product: DPDK
Version: 21.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: vsrivast@xilinx.com
Target Milestone: ---
In the 21.11_rc2 code base there are some changes in the function
rte_devargs_layers_parse (in the lib/eal/common/eal_common_devargs.c) due to
these changes an issue got introduced which is resulting junk value for
'devargs.bus_str' in the function rte_dev_iterator_init for
RTE_DEVARGS_KEY_CLASS case.
- Earlier devargs->bus_str was getting populated for all the cases of
RTE_DEVARGS_KEY_*(_CLASS/_BUS/_DRIVER) in the rte_devargs_layers_parse.
- In the latest code it is getting populated only for RTE_DEVARGS_KEY_BUS so
for all other cases it has junk value for 'devargs.bus_str' if devargs fields
are NOT set to 0 by caller function.
- rte_dev_iterator_init is calling rte_devargs_layers_parse() and it does not
set devargs fields to 0 before passing it to rte_devargs_layers_parse so for
RTE_DEVARGS_KEY_CLASS case devargs->bus_str is having junk value which is
causing issue.
- When running dpdk-vdpa app then it is unable to find vDPA device Due to this
issue.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-10-28 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 17:55 bugzilla [this message]
2021-11-04 10:50 ` 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-862-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).