From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: "Lothar Waßmann" <LW@KARO-electronics.de>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Akinobu Mita <akinobu.mita@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Huang Shijie <b32955@freescale.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: mtd_oobtest: fix verify errors due to incorrect use of prandom_bytes_state()
Date: Wed, 22 Jan 2014 15:09:59 +0100 [thread overview]
Message-ID: <20140122150959.78cf2827@ipc1.ka-ro> (raw)
In-Reply-To: <1389608739-10945-1-git-send-email-LW@KARO-electronics.de>
Hi,
Is anyone taking care of this?
Lothar Waßmann wrote:
> When using prandom_bytes_state() it is critical to use the same block
> size in all invocations that are to produce the same random sequence.
> Otherwise the state of the PRNG will be out of sync if the blocksize
> is not divisible by 4.
> This leads to bogus verification errors in several tests which use
> different block sizes to initialize the buffer for writing and
> comparison.
>
> Signed-off-by: Lothar Waßmann <LW@KARO-electronics.de>
> ---
> drivers/mtd/tests/oobtest.c | 14 ++++++++++++--
> 1 files changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/tests/oobtest.c b/drivers/mtd/tests/oobtest.c
> index 2e9e2d1..72c7359 100644
> --- a/drivers/mtd/tests/oobtest.c
> +++ b/drivers/mtd/tests/oobtest.c
> @@ -213,8 +213,15 @@ static int verify_eraseblock_in_one_go(int ebnum)
> int err = 0;
> loff_t addr = ebnum * mtd->erasesize;
> size_t len = mtd->ecclayout->oobavail * pgcnt;
> + int i;
> +
> + for (i = 0; i < pgcnt; i++)
> + prandom_bytes_state(&rnd_state, &writebuf[i * use_len],
> + use_len);
> + if (len % use_len)
> + prandom_bytes_state(&rnd_state, &writebuf[i * use_len],
> + len % use_len);
>
> - prandom_bytes_state(&rnd_state, writebuf, len);
> ops.mode = MTD_OPS_AUTO_OOB;
> ops.len = 0;
> ops.retlen = 0;
> @@ -594,7 +601,10 @@ static int __init mtd_oobtest_init(void)
> if (bbt[i] || bbt[i + 1])
> continue;
> prandom_bytes_state(&rnd_state, writebuf,
> - mtd->ecclayout->oobavail * 2);
> + mtd->ecclayout->oobavail);
> + prandom_bytes_state(&rnd_state,
> + writebuf + mtd->ecclayout->oobavail,
> + mtd->ecclayout->oobavail);
> addr = (i + 1) * mtd->erasesize - mtd->writesize;
> ops.mode = MTD_OPS_AUTO_OOB;
> ops.len = 0;
--
___________________________________________________________
Ka-Ro electronics GmbH | Pascalstraße 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Geschäftsführer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
www.karo-electronics.de | info@karo-electronics.de
___________________________________________________________
next prev parent reply other threads:[~2014-01-22 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 10:25 [PATCH] mtd: mtd_oobtest: fix verify errors due to incorrect use of prandom_bytes_state() Lothar Waßmann
2014-01-22 14:09 ` Lothar Waßmann [this message]
2014-01-22 14:31 ` Akinobu Mita
2014-01-22 15:41 ` Lothar Waßmann
2014-01-22 23:25 ` Akinobu Mita
2014-01-23 5:51 ` Lothar Waßmann
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=20140122150959.78cf2827@ipc1.ka-ro \
--to=lw@karo-electronics.de \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=artem.bityutskiy@linux.intel.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox