From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
James Bottomley <JBottomley@Odin.com>,
linux-kernel@vger.kernel.org,
"K. Y. Srinivasan" <kys@microsoft.com>
Subject: Re: [PATCH v4 2/2] lib/test-string_helpers.c: add string_get_size() tests
Date: Wed, 16 Sep 2015 14:33:07 +0300 [thread overview]
Message-ID: <1442403187.8361.62.camel@linux.intel.com> (raw)
In-Reply-To: <87h9mu4nkb.fsf@rasmusvillemoes.dk>
On Wed, 2015-09-16 at 13:21 +0200, Rasmus Villemoes wrote:
> On Tue, Sep 15 2015, Andy Shevchenko <
> andriy.shevchenko@linux.intel.com> wrote:
>
> > On Tue, 2015-09-15 at 15:55 +0200, Vitaly Kuznetsov wrote:
> > > +static __init void test_string_get_size_one(u64 size, u64
> > > blk_size,
> > > + const enum
> > > string_size_units units,
> > > + const char
> > > *exp_result)
> > > +{
> > > + char buf[16];
> > > +
> > > + string_get_size(size, blk_size, units, buf,
> > > sizeof(buf));
> > > + if (!memcmp(buf, exp_result, strnlen(exp_result,
> > > sizeof(buf)
> > > - 1) + 1))
> >
> > Actually you don't need to do this +- 1. Either you will have '\0'
> > or
> > not, it will be checked by memcmp() anyway.
> >
> > Thus,
> > memcmp(buf, exp_result, strnlen(exp_result, sizeof(buf))).
>
> Huh? How does that ensure that string_get_size put a '\0' at the
> right
> spot? We do need the comparison to also cover the terminating '\0' in
> exp_result.
Ah, you are right.
But seems we have length of the exp_result always smaller than buffer
size, so, would we change this to
memcmp(…, strlen(exp_result) + 1);
?
> [It would be nice if we could assert at compile-time that
> strlen(exp_result) < sizeof(buf).]
Interesting if BUILD_BUG_ON can help here. Can we use
sizeof(exp_result) since all of them are literal constants?
>
> > Perhaps one line comment here
> > /* Make sure that buf will be always NULL-terminated */
> >
> > > + buf[sizeof(buf) - 1] = '\0';
>
> <bikeshed>Could we pretty-please use different names for 0 the
> pointer
> and 0 the character, say in this case nul or NUL or '\0' or simply
> 0. Also, I don't see the value of the comment; that line is a totally
> standard idiom.</bikeshed>.
Got your point.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2015-09-16 11:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 13:55 [PATCH v4 0/2] lib/string_helpers.c: fix infinite loop in string_get_size() Vitaly Kuznetsov
2015-09-15 13:55 ` [PATCH v4 1/2] " Vitaly Kuznetsov
2015-09-15 13:55 ` [PATCH v4 2/2] lib/test-string_helpers.c: add string_get_size() tests Vitaly Kuznetsov
2015-09-15 15:20 ` Andy Shevchenko
2015-09-16 11:21 ` Rasmus Villemoes
2015-09-16 11:33 ` Andy Shevchenko [this message]
2015-09-16 16:34 ` Vitaly Kuznetsov
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=1442403187.8361.62.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=JBottomley@Odin.com \
--cc=akpm@linux-foundation.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=vkuznets@redhat.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).