From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 6/7] test_hexdump: test all possible group sizes for overflow
Date: Fri, 20 Nov 2015 18:43:59 +0200 [thread overview]
Message-ID: <1448037839.31665.172.camel@linux.intel.com> (raw)
In-Reply-To: <87h9kis3co.fsf@rasmusvillemoes.dk>
On Thu, 2015-11-19 at 11:14 +0100, Rasmus Villemoes wrote:
> On Wed, Nov 11 2015, Andy Shevchenko <andriy.shevchenko@linux.intel.c
> om> wrote:
>
> > Currently only one combination is tested for overflow, i.e. rowsize
> > = 16,
> > groupsize = 1, len = 1. Do various test to go all possible
> > branches.
[]
> > + do {
> > + int gs = 1 << i;
> > + size_t len = get_random_int() % 16 + gs;
> > +
> > + test_hexdump_overflow(buflen, rounddown(len, gs),
> > 16, gs, ascii);
> > + } while (i++ < 3);
> > +}
>
>
> aren't you missing a
>
> test_hexdump_overflow(buflen, rounddown(len, gs), 32, gs, ascii);
>
> here to also exercise the rowsize==32 code?
I could add that as well, though it seems minor since the idea is to go
for all branches, which 16 covers anyway.
> static int __init test_hexdump_init(void)
> > {
> > unsigned int i;
> > @@ -186,10 +199,10 @@ static int __init test_hexdump_init(void)
> > test_hexdump_set(rowsize, true);
> >
> > for (i = 0; i <= TEST_HEXDUMP_BUF_SIZE; i++)
> > - test_hexdump_overflow(i, false);
> > + test_hexdump_overflow_set(i, false);
> >
> > for (i = 0; i <= TEST_HEXDUMP_BUF_SIZE; i++)
> > - test_hexdump_overflow(i, true);
> > + test_hexdump_overflow_set(i, true);
>
> It seems neater to do one loop:
>
> for (i = 0; i <= TEST_HEXDUMP_BUF_SIZE; i++) {
> test_hexdump_overflow_set(i, false);
> test_hexdump_overflow_set(i, true);
> }
I would like to keep them separately, though I'm also okay to do it in
one loop.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2015-11-20 16:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 16:35 [PATCH v1 0/7] hexdump: update test suite Andy Shevchenko
2015-11-11 16:35 ` [PATCH v1 1/7] test_hexdump: rename to test_hexdump Andy Shevchenko
2015-11-19 10:05 ` Rasmus Villemoes
2015-11-11 16:35 ` [PATCH v1 2/7] test_hexdump: introduce test_hexdump_prepare_test() helper Andy Shevchenko
2015-11-19 10:05 ` Rasmus Villemoes
2015-11-11 16:35 ` [PATCH v1 3/7] test_hexdump: go through all possible lengths of buffer Andy Shevchenko
2015-11-19 10:07 ` Rasmus Villemoes
2015-11-20 16:58 ` Andy Shevchenko
2015-11-23 8:59 ` Rasmus Villemoes
2015-11-26 15:22 ` Andy Shevchenko
2015-11-11 16:35 ` [PATCH v1 4/7] test_hexdump: replace magic numbers by their meaning Andy Shevchenko
2015-11-19 10:08 ` Rasmus Villemoes
2015-11-20 16:56 ` Andy Shevchenko
2015-11-11 16:35 ` [PATCH v1 5/7] test_hexdump: check all bytes in real buffer Andy Shevchenko
2015-11-19 10:11 ` Rasmus Villemoes
2015-11-20 16:55 ` Andy Shevchenko
2015-11-23 9:28 ` Rasmus Villemoes
2015-11-11 16:35 ` [PATCH v1 6/7] test_hexdump: test all possible group sizes for overflow Andy Shevchenko
2015-11-19 10:14 ` Rasmus Villemoes
2015-11-20 16:43 ` Andy Shevchenko [this message]
2015-11-23 9:36 ` Rasmus Villemoes
2015-11-11 16:35 ` [PATCH v1 7/7] test_hexdump: print statistics at the end Andy Shevchenko
2015-11-19 10:16 ` Rasmus Villemoes
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=1448037839.31665.172.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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