From: "Jastrzebski, MichalX K" <michalx.k.jastrzebski@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Mrzyglod, DanielX T" <danielx.t.mrzyglod@intel.com>,
Olivier MATZ <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] cmdline: fix type format from unsigned to size_t for buffer size
Date: Tue, 24 Mar 2015 10:48:25 +0000 [thread overview]
Message-ID: <60ABE07DBB3A454EB7FAD707B4BB158213902C97@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <2042259.HzLBmuaM6Z@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, March 23, 2015 12:47 PM
> To: Mrzyglod, DanielX T
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] cmdline: fix type format from unsigned to
> size_t for buffer size
>
> Daniel,
> Without answer to the question from Olivier, this patch is going to be
> ignored.
>
> 2015-02-24 12:03, Olivier MATZ:
> > Hi Daniel,
> >
> > On 02/20/2015 05:18 PM, Daniel Mrzyglod wrote:
> > > Function match_inst is used to take buffor using sizeof() which is size_t
> type.
> > > This modification also involved changing '%u' to '%zu' in printf function.
> > >
> > > Signed-off-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
> > > ---
> > > lib/librte_cmdline/cmdline_parse.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/lib/librte_cmdline/cmdline_parse.c
> b/lib/librte_cmdline/cmdline_parse.c
> > > index dfc885c..0821791 100644
> > > --- a/lib/librte_cmdline/cmdline_parse.c
> > > +++ b/lib/librte_cmdline/cmdline_parse.c
> > > @@ -138,7 +138,7 @@ nb_common_chars(const char * s1, const char *
> s2)
> > > */
> > > static int
> > > match_inst(cmdline_parse_inst_t *inst, const char *buf,
> > > - unsigned int nb_match_token, void *resbuf, unsigned resbuf_size)
> > > + unsigned int nb_match_token, void *resbuf, size_t resbuf_size)
> > > {
> > > unsigned int token_num=0;
> > > cmdline_parse_token_hdr_t * token_p;
> > > @@ -169,7 +169,7 @@ match_inst(cmdline_parse_inst_t *inst, const
> char *buf,
> > >
> > > if (token_hdr.offset > resbuf_size) {
> > > printf("Parse error(%s:%d): Token offset(%u)
> "
> > > - "exceeds maximum size(%u)\n",
> > > + "exceeds maximum size(%zu)\n",
> > > __FILE__, __LINE__,
> > > token_hdr.offset, resbuf_size);
> > > return -ENOBUFS;
> > >
> >
> >
> > Did you see a specific issue with the current code? (maybe a compilation
> > issue or a klocwork issue?)
Hi Olivier, Thomas
Yes, this is an issue reported by the static analysis tool.
> >
> > I think this patch is ok, but there are many places where this kind
> > of fixes should be applied in cmdline (cmdline_parse_*(),
> > cmdline_get_help_*(), etc.). Is there a motivation for changing it
> > only there?
The tool we use didn't reported other places,
that is why Daniel send only this one change.
> >
> > Regards,
> > Olivier
> >
>
next prev parent reply other threads:[~2015-03-24 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 16:18 Daniel Mrzyglod
2015-02-24 11:03 ` Olivier MATZ
2015-03-23 11:46 ` Thomas Monjalon
2015-03-24 10:48 ` Jastrzebski, MichalX K [this message]
2015-03-24 11:19 ` Olivier MATZ
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=60ABE07DBB3A454EB7FAD707B4BB158213902C97@IRSMSX109.ger.corp.intel.com \
--to=michalx.k.jastrzebski@intel.com \
--cc=danielx.t.mrzyglod@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=thomas.monjalon@6wind.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).