From: "Stojaczyk, Dariusz" <dariusz.stojaczyk@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "gaetan.rivet@6wind.com" <gaetan.rivet@6wind.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Guo, Jia" <jia.guo@intel.com>
Subject: Re: [dpdk-dev] [PATCH] devargs: do not replace already inserted devargs
Date: Thu, 8 Nov 2018 11:25:17 +0000 [thread overview]
Message-ID: <FBE7E039FA50BF47A673AD0BD3CD56A84622B969@HASMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <20181107232105.19187-1-thomas@monjalon.net>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Thursday, November 8, 2018 12:21 AM
> To: dev@dpdk.org
> Cc: gaetan.rivet@6wind.com; Zhang, Qi Z <qi.z.zhang@intel.com>; Guo, Jia
> <jia.guo@intel.com>; Stojaczyk, Dariusz <dariusz.stojaczyk@intel.com>
> Subject: [PATCH] devargs: do not replace already inserted devargs
>
> The devargs of a device can be replaced by a newly allocated one
> when trying to probe again the same device (multi-process or
> multi-ports scenarios). This is breaking some pointer references.
>
> It can be avoided by copying the new content, freeing the new devargs,
> and returning the already inserted pointer.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
Tested-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
next prev parent reply other threads:[~2018-11-08 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 23:21 Thomas Monjalon
2018-11-08 11:25 ` Stojaczyk, Dariusz [this message]
2018-11-08 12:26 ` Thomas Monjalon
2018-11-08 12:35 ` Stojaczyk, Dariusz
2018-11-08 12:53 ` Thomas Monjalon
2018-11-08 17:12 ` Zhang, Qi Z
2018-11-11 23:12 ` Thomas Monjalon
2018-11-08 14:02 ` Slava Ovsiienko
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=FBE7E039FA50BF47A673AD0BD3CD56A84622B969@HASMSX105.ger.corp.intel.com \
--to=dariusz.stojaczyk@intel.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
--cc=jia.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--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).