From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mem: fix static analysis warning
Date: Fri, 20 Jul 2018 11:30:00 +0200 [thread overview]
Message-ID: <2541590.gd5fToPQqf@xps> (raw)
In-Reply-To: <8308ba8ca44234ec58b36c422ff3bb85117ecd08.1531841506.git.anatoly.burakov@intel.com>
17/07/2018 17:41, Anatoly Burakov:
> Technically, single file segments codepath will never get
> triggered when using in-memory mode, because EAL prohibits
> mixing these two options at initialization time. However,
> code analyzers do not know that, and some will complain
> about either using uninitialized variables, or trying to
> do operations on an already closed descriptor.
>
> Fix this by assuring the compiler or code analyzer that
> in-memory mode code never gets triggered when using
> single-file segments mode.
>
> Coverity ID: 302847
> Fixes: 72b49ff623c4 ("mem: support --in-memory mode")
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-07-20 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 15:41 Anatoly Burakov
2018-07-20 9:30 ` Thomas Monjalon [this message]
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=2541590.gd5fToPQqf@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--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).