public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Nahor <nahor.j+gmane@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: [PATCH] [MTD-UTILS] Incorrect loop condition
Date: Wed, 03 Jun 2009 18:18:25 -0700	[thread overview]
Message-ID: <h077d2$ra9$1@ger.gmane.org> (raw)

Hi all,

Here is a small patch to fix an obvious typo.

If the file contains only a few bytes in the last page and the padding 
option is selected, the loop may exit early (readlen < meminfo.oobsize).
Most of the time it will still work though because the code tries to 
read the whole OOB in one chunk.


On a similar issue, shouldn't the loop reading the input file exit with 
error if cnt == 0? The loop should alread exit when all the expected 
data is read. So if cnt == 0, it means that nandwrite didn't get all the 
data it wanted. The code then goes on as if everything was correctly 
read so it will write the data from the previous page. This is a 
security risk (even though the necessary conditions make it nearly 
impossible in practice).


Regards,
    Nahor



--- a/nandwrite.c        2009-06-01 18:03:55.000000000 -0700
+++ b/nandwrite.c 2009-06-03 15:29:24.000000000 -0700
@@ -531,7 +531,7 @@
                if (writeoob) {
                        int tinycnt = 0;

-                       while(tinycnt < readlen) {
+                       while(tinycnt < meminfo.oobsize) {
                                cnt = read(ifd, oobreadbuf + tinycnt,
meminfo.oobsize - tinycnt);
                                if (cnt == 0) { // EOF
                                        break;

             reply	other threads:[~2009-06-04  1:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04  1:18 Nahor [this message]
2009-06-05 12:15 ` [PATCH] [MTD-UTILS] Incorrect loop condition Artem Bityutskiy
2009-06-06  1:45   ` Jehan Bing
2009-06-08  6:09     ` Artem Bityutskiy

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='h077d2$ra9$1@ger.gmane.org' \
    --to=nahor.j+gmane@gmail.com \
    --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