From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] test: fix missing NULL pointer checks
Date: Mon, 26 Jan 2015 22:26:46 +0100 [thread overview]
Message-ID: <5122600.hXUxZ4V3cS@xps13> (raw)
In-Reply-To: <20867625.qP6gkIlEQ3@xps13>
Ping. What next for this patch?
2014-12-18 22:05, Thomas Monjalon:
> 2014-12-18 09:41, Daniel Mrzyglod:
> > In test_sched, we are missing NULL pointer checks after calls to create the
> > mempool and to allocate an mbuf. Add in these checks using VERIFY macros.
> >
> > Signed-off-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
> > ---
> > app/test/test_sched.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/app/test/test_sched.c b/app/test/test_sched.c
> > index c957d80..9b6e037 100644
> > --- a/app/test/test_sched.c
> > +++ b/app/test/test_sched.c
> > @@ -166,6 +166,7 @@ test_sched(void)
> > int err;
> >
> > mp = create_mempool();
> > + VERIFY(mp != NULL,"Error create mempool\n");
>
> A space is missing after the comma.
> Is "Error creating mempool" more correct?
>
> > port_param.socket = 0;
> > port_param.rate = (uint64_t) 10000 * 1000 * 1000 / 8;
> > @@ -184,6 +185,7 @@ test_sched(void)
> >
> > for (i = 0; i < 10; i++) {
> > in_mbufs[i] = rte_pktmbuf_alloc(mp);
> > + VERIFY(in_mbufs[i] != NULL, "Bad packet allocation");
>
> An \n is missing.
> "Packet allocation failed" seems more appropriate.
next prev parent reply other threads:[~2015-01-26 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 9:41 Daniel Mrzyglod
2014-12-18 21:05 ` Thomas Monjalon
2015-01-26 21:26 ` Thomas Monjalon [this message]
2014-12-18 21:12 ` Neil Horman
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=5122600.hXUxZ4V3cS@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=danielx.t.mrzyglod@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).