From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: David Christensen <drc@linux.vnet.ibm.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 2/4] test: verify calloc succeeded for sum variable
Date: Tue, 7 May 2019 10:40:54 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772580148AA21AA@irsmsx105.ger.corp.intel.com> (raw)
Message-ID: <20190507104054.Tx1CzMmX2pZJ_KkJLf-hqLaeMJFuCtWTAEGzqnJCkyQ@z> (raw)
In-Reply-To: <1557170620-99694-1-git-send-email-drc@linux.vnet.ibm.com>
> Code tested calloc failures for pt & lpt variables
> but not for the sum variable. Add a test for calloc
> failure of sum.
>
> Signed-off-by: David Christensen <drc@linux.vnet.ibm.com>
> ---
> v2:
> * Removed change to ITER_MAX
>
> app/test/test_barrier.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/app/test/test_barrier.c b/app/test/test_barrier.c
> index c219d56..ae37b1e 100644
> --- a/app/test/test_barrier.c
> +++ b/app/test/test_barrier.c
> @@ -202,7 +202,7 @@ struct lcore_plock_test {
> printf("%s(iter=%u, utype=%u) started on %u lcores\n",
> __func__, iter, utype, n);
>
> - if (pt == NULL || lpt == NULL) {
> + if (pt == NULL || lpt == NULL || sum == NULL) {
> printf("%s: failed to allocate memory for %u lcores\n",
> __func__, n);
> free(pt);
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 1.8.3.1
next prev parent reply other threads:[~2019-05-07 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 19:23 David Christensen
2019-05-06 19:23 ` David Christensen
2019-05-07 10:40 ` Ananyev, Konstantin [this message]
2019-05-07 10:40 ` Ananyev, Konstantin
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=2601191342CEEE43887BDE71AB9772580148AA21AA@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.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).