From: Sascha Hauer <s.hauer@pengutronix.de>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 7/7] nand-bb: implement lseek in readonly mode
Date: Thu, 15 Dec 2011 16:21:33 +0100 [thread overview]
Message-ID: <20111215152133.GT27267@pengutronix.de> (raw)
In-Reply-To: <87y5uevt77.fsf@free.fr>
On Thu, Dec 15, 2011 at 02:51:40PM +0100, Robert Jarzmik wrote:
> 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
Yup, that's wrong. We have to add 16 to raw_pos here, not 2.
> - loop4:
> now=2
> ret=0 (B3 good)
> offset = 0
> raw_pos = 36
> bb->offset = 36
> return 34
Funny enough that my code actually works. In loop4 we have ret=1
because we are still on B2 (raw_pos is 34, -> still in block 2).
Now the code loops over Block2 in small steps until it comes to
block3 and returns with the correct raw offset, so I didn't see
this in my tests.
>
> 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
This one should work like expected:
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;
} else {
raw_pos += bb->info.erasesize
}
if (!offset) {
bb->offset = raw_pos;
return __offset;
}
}
loop1:
now = 16
ret = 0
offset = 18
raw_pos = 16
loop2:
now = 16
ret = 0
offset = 2
raw_pos = 32
loop3:
now = 2
ret = 1
offset = 2
raw_pos = 48
loop4:
now = 2
ret = 0
offset = 0
raw_pos = 50
Thanks for catching this.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-12-15 15:21 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
2011-12-15 15:21 ` Sascha Hauer [this message]
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=20111215152133.GT27267@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=robert.jarzmik@free.fr \
/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.