From: Qi Zhang <qi.z.zhang@intel.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org, Qi Zhang <qi.z.zhang@intel.com>
Subject: [dpdk-dev] [PATCH] eal: fix floating device argument pointer
Date: Mon, 22 Oct 2018 13:49:32 +0800 [thread overview]
Message-ID: <20181022054932.39052-1-qi.z.zhang@intel.com> (raw)
After we insert a devargs into devargs_list, following bus->scan may
destroy it due to another rte_devargs_insert. Its better not to use
a devargs pointer after it has been inserted.
Fixes: 911462eb4a5f ("eal: simplify parameters of hotplug functions")
Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
---
lib/librte_eal/common/eal_common_dev.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/lib/librte_eal/common/eal_common_dev.c b/lib/librte_eal/common/eal_common_dev.c
index 8b0844af1..d4b1ea70d 100644
--- a/lib/librte_eal/common/eal_common_dev.c
+++ b/lib/librte_eal/common/eal_common_dev.c
@@ -185,6 +185,7 @@ local_dev_probe(const char *devargs, struct rte_device **new_dev)
{
struct rte_device *dev;
struct rte_devargs *da;
+ struct rte_devargs da_cp;
int ret;
*new_dev = NULL;
@@ -203,18 +204,23 @@ local_dev_probe(const char *devargs, struct rte_device **new_dev)
goto err_devarg;
}
+ /**
+ * its better not to use da after rte_devargs_insert,
+ * so make a copy here.
+ */
+ da_cp = *da;
ret = rte_devargs_insert(da);
if (ret)
goto err_devarg;
- ret = da->bus->scan();
+ ret = da_cp.bus->scan();
if (ret)
goto err_devarg;
- dev = da->bus->find_device(NULL, cmp_dev_name, da->name);
+ dev = da_cp.bus->find_device(NULL, cmp_dev_name, da_cp.name);
if (dev == NULL) {
RTE_LOG(ERR, EAL, "Cannot find device (%s)\n",
- da->name);
+ da_cp.name);
ret = -ENODEV;
goto err_devarg;
}
--
2.13.6
next reply other threads:[~2018-10-22 5:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 5:49 Qi Zhang [this message]
2018-10-22 7:25 ` Thomas Monjalon
2018-10-23 22:39 ` Gaëtan Rivet
2018-10-24 14:43 ` Thomas Monjalon
2018-10-24 15:33 ` Gaëtan Rivet
2018-10-25 3:22 ` Zhang, Qi Z
2018-10-25 9:42 ` Gaëtan Rivet
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=20181022054932.39052-1-qi.z.zhang@intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).