From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 7/7] nand-bb: implement lseek in readonly mode
Date: Thu, 15 Dec 2011 14:51:40 +0100 [thread overview]
Message-ID: <87y5uevt77.fsf@free.fr> (raw)
In-Reply-To: <1323946179-9883-8-git-send-email-s.hauer@pengutronix.de> (Sascha Hauer's message of "Thu, 15 Dec 2011 11:49:39 +0100")
Sascha Hauer <s.hauer@pengutronix.de> writes:
> +static off_t nand_bb_lseek(struct cdev *cdev, off_t __offset)
> +{
> + struct nand_bb *bb = cdev->priv;
> + unsigned long raw_pos = 0;
> + uint32_t offset = __offset;
> + int ret;
> +
> + /* lseek only in readonly mode */
> + if (bb->flags & O_ACCMODE)
> + return -ENOSYS;
> +
> + while (raw_pos < bb->raw_size) {
> + off_t now = min(offset, bb->info.erasesize);
> +
> + ret = cdev_ioctl(bb->cdev_parent, MEMGETBADBLOCK, (void *)raw_pos);
> + if (ret < 0)
> + return ret;
> + if (!ret)
> + offset -= now;
> + raw_pos += now;
> + if (!offset) {
> + bb->offset = raw_pos;
> + return __offset;
> + }
> + }
Are you sure of this algorithm ?
I tried to check it with:
- erasesize=16 (silly I know, but it's simpler for my mind)
- bb->raw_size = +oo
- offset = 34
Let's assume we have eraseblock B0, B1, B2 and B3 of 16 bytes.
B0, B1 and B3 are good, B2 is a bad block.
+--------+--------+--------+--------+
| B0 | B1 |xxxB2xxx| B3 |
+--------+--------+--------+--------+
If I unroll the while loop:
- loop1:
now=16
ret=0 (B0 good)
offset = 18
raw_pos = 16
- loop2:
now=16
ret=0 (B1 good)
offset = 2
raw_pos = 32
- loop3:
now=2
ret=1 (B2 bad)
offset = 2
raw_pos = 34
- loop4:
now=2
ret=0 (B3 good)
offset = 0
raw_pos = 36
bb->offset = 36
return 34
So we end up with bb->offset = 36, which seems incorrect to me. I would have
understood a value of 50, but 36 ... I don't
Cheers.
--
Robert
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-12-15 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 10:49 misc patches Sascha Hauer
2011-12-15 10:49 ` [PATCH 1/7] remove unused watchdog header Sascha Hauer
2011-12-15 10:49 ` [PATCH 2/7] remove unused keyboard.h file Sascha Hauer
2011-12-15 10:49 ` [PATCH 3/7] ARM cpuinfo: decode more bits, use ARRAY_SIZE Sascha Hauer
2011-12-15 10:49 ` [PATCH 4/7] ARM: remove unused icache command Sascha Hauer
2011-12-15 10:49 ` [PATCH 5/7] common.h: remove unused function declarations Sascha Hauer
2011-12-15 10:49 ` [PATCH 6/7] cdev: pass flags to open function Sascha Hauer
2011-12-15 10:49 ` [PATCH 7/7] nand-bb: implement lseek in readonly mode Sascha Hauer
2011-12-15 13:51 ` Robert Jarzmik [this message]
2011-12-15 15:21 ` Sascha Hauer
2011-12-15 15:51 ` Robert Jarzmik
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=87y5uevt77.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.