From: Joe Perches <joe@perches.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>,
Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Torsten Duwe <duwe@lst.de>, "Theodore Ts'o" <tytso@mit.edu>,
Amit Shah <amit.shah@redhat.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Kees Cook <keescook@chromium.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3v] char: hw_random: core.c: Changed from using strncat to strlcat
Date: Thu, 16 Oct 2014 10:55:57 -0700 [thread overview]
Message-ID: <1413482157.8915.3.camel@perches.com> (raw)
In-Reply-To: <20141016174823.GM17447@titan.lakedaemon.net>
On Thu, 2014-10-16 at 13:48 -0400, Jason Cooper wrote:
> On Thu, Oct 16, 2014 at 10:25:03AM -0700, Joe Perches wrote:
> > On Thu, 2014-10-16 at 19:15 +0200, Rickard Strandqvist wrote:
> > > The buf is used to hold the list of hwrng devices registered.
> > > The old code ensures we don't walk off the end of buf as we
> > > fill it, but it's unnecessarily complicated and thus difficult
> > > to maintain. Simplify it by using strlcat.
> > > We also ensure the string within buf is NULL terminated
> > > so the final strlen is ok.
> > []
> > > diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
> > []
> > > @@ -289,16 +288,13 @@ static ssize_t hwrng_attr_available_show(struct device *dev,
> > > return -ERESTARTSYS;
> > > buf[0] = '\0';
> > > list_for_each_entry(rng, &rng_list, list) {
> > > - strncat(buf, rng->name, PAGE_SIZE - ret - 1);
> > > - ret += strlen(rng->name);
> > > - strncat(buf, " ", PAGE_SIZE - ret - 1);
> > > - ret++;
> > > + strlcat(buf, rng->name, PAGE_SIZE);
> > > + strlcat(buf, " ", PAGE_SIZE);
> > > }
> > > - strncat(buf, "\n", PAGE_SIZE - ret - 1);
> > > - ret++;
> > > + strlcat(buf, "\n", PAGE_SIZE);
> > > mutex_unlock(&rng_mutex);
> > >
> > > - return ret;
> > > + return strlen(buf);
> > > }
> > >
> > > static DEVICE_ATTR(rng_current, S_IRUGO | S_IWUSR,
> >
> > Rickard, can you please use some optimizations here
> > (and elsewhere) so that strlcat doesn't always have
> > to strlen the first string and the return doesn't
> > have to do the strlen too?
>
> Joe, is further optimization worth the effort? This function is only
> called when the end user reads the sysfs file rng_available...
It's unlikely that it matters much here.
I just don't like the repeated and unnecessary strlen.
I do imagine this pattern being repeated though where
it does matter.
next prev parent reply other threads:[~2014-10-16 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 17:15 Rickard Strandqvist
2014-10-16 17:25 ` Joe Perches
2014-10-16 17:41 ` Rickard Strandqvist
2014-10-16 17:53 ` Joe Perches
2014-10-16 17:48 ` Jason Cooper
2014-10-16 17:55 ` Joe Perches [this message]
2014-10-16 18:05 ` Jason Cooper
2014-10-16 18:11 ` Rickard Strandqvist
2014-10-16 17:53 ` Jason Cooper
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=1413482157.8915.3.camel@perches.com \
--to=joe@perches.com \
--cc=amit.shah@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=duwe@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=jason@lakedaemon.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=paul.gortmaker@windriver.com \
--cc=rickard_strandqvist@spectrumdigital.se \
--cc=sboyd@codeaurora.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®