All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH 4/5] replace snprintf with strlcpy without adding extra include
Date: Thu, 04 Apr 2019 20:05:06 +0200	[thread overview]
Message-ID: <4698261.tayNczNUhG@xps> (raw)
In-Reply-To: <20190403155638.GA1336@bricha3-MOBL.ger.corp.intel.com>

03/04/2019 17:56, Bruce Richardson:
> On Wed, Apr 03, 2019 at 08:51:32AM -0700, Stephen Hemminger wrote:
> > On Wed,  3 Apr 2019 15:45:04 +0100
> > Bruce Richardson <bruce.richardson@intel.com> wrote:
> > 
> > > diff --git a/lib/librte_ring/rte_ring.c b/lib/librte_ring/rte_ring.c
> > > index d215acecc..a542f6f5d 100644
> > > --- a/lib/librte_ring/rte_ring.c
> > > +++ b/lib/librte_ring/rte_ring.c
> > > @@ -78,7 +78,7 @@ rte_ring_init(struct rte_ring *r, const char *name, unsigned count,
> > >  
> > >  	/* init the ring structure */
> > >  	memset(r, 0, sizeof(*r));
> > > -	ret = snprintf(r->name, sizeof(r->name), "%s", name);
> > > +	ret = strlcpy(r->name, name, sizeof(r->name));
> > >  	if (ret < 0 || ret >= (int)sizeof(r->name))
> > 
> > I would rather use the name length that is part of the header file.
> > 
> > 	if (strnlen(name, RTE_RING_NAMESIZE) == RTE_RING_NAMESIZE)
> > 		return -ENAMETOOLONG;
> > 
> > 	strlcpy(r->name, name, sizeof(r->name))
> >
> Yes, though honestly it's a matter of preference. Since this was a scripted
> replacement each change wasn't checked in too much detail other than a
> cursory check for correctness.

I prefer using sizeof/strlen rather than the constant used for allocation.
Reasons are:
	- it's easier to understand the intent
	- it's easier to change how the allocation size is chosen

  reply	other threads:[~2019-04-04 18:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 14:45 [PATCH 0/5] clean up snprintf use for string copying Bruce Richardson
2019-04-03 14:45 ` [PATCH 1/5] net/bonding: fix buffer length when printing strings Bruce Richardson
2019-04-03 15:47   ` Stephen Hemminger
2019-04-03 15:51     ` Bruce Richardson
2019-04-03 15:53       ` Stephen Hemminger
2019-04-03 14:45 ` [PATCH 2/5] devtools/cocci: make strlcpy replacement smarter Bruce Richardson
2019-04-03 14:45 ` [PATCH 3/5] devtools/cocci: create safer version of strlcpy script Bruce Richardson
2019-04-03 14:45 ` [PATCH 4/5] replace snprintf with strlcpy without adding extra include Bruce Richardson
2019-04-03 15:51   ` Stephen Hemminger
2019-04-03 15:56     ` Bruce Richardson
2019-04-04 18:05       ` Thomas Monjalon [this message]
2019-04-03 14:45 ` [PATCH 5/5] replace snprintf with strlcpy Bruce Richardson
2019-04-03 14:57 ` [PATCH 0/5] clean up snprintf use for string copying Wiles, Keith
2019-04-03 15:13   ` Bruce Richardson
2019-04-03 15:27   ` Stephen Hemminger
2019-04-04 20:11 ` Thomas Monjalon

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=4698261.tayNczNUhG@xps \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.