From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Arnon Warshavsky <arnon@qwilt.com>,
dev@dpdk.org, david.marchand@redhat.com, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] eal: unmap undesired address upon config reattach failure
Date: Mon, 19 Aug 2019 15:48:39 +0100 [thread overview]
Message-ID: <0ee1f694-b2c6-43fc-6eef-988ef5e11746@intel.com> (raw)
In-Reply-To: <1566223064-19932-1-git-send-email-arnon@qwilt.com>
On 19-Aug-19 2:57 PM, Arnon Warshavsky wrote:
> Have rte_eal_config_reattach clean up the mapped address
> which is a valid address but not the one intended.
>
> Coverity issue: 343439
> Fixes: 4e8854ae89fa ("eal: do not panic on shared memory init")
> Fixes: b149a7064261 ("eal/freebsd: add config reattach in secondary")
> Signed-off-by: Arnon Warshavsky <arnon@qwilt.com>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-08-19 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 6:47 [dpdk-dev] [PATCH] " Arnon Warshavsky
2019-08-19 8:27 ` David Marchand
2019-08-19 13:57 ` [dpdk-dev] [PATCH v2] " Arnon Warshavsky
2019-08-19 14:48 ` Burakov, Anatoly [this message]
2019-08-19 15:29 ` David Marchand
2019-10-15 18:39 ` David Marchand
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=0ee1f694-b2c6-43fc-6eef-988ef5e11746@intel.com \
--to=anatoly.burakov@intel.com \
--cc=arnon@qwilt.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
/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).