From: Alexander Belyakov <alexander.belyakov@intel.com>
To: Ferenc Havasi <havasi@inf.u-szeged.hu>
Cc: Holger Schurig <h.schurig@mn-solutions.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-mtd@lists.infradead.org
Subject: Re: Problem of "JFFS2 summary"
Date: Tue, 18 Apr 2006 12:06:22 +0400 [thread overview]
Message-ID: <44449DFE.6040905@intel.com> (raw)
In-Reply-To: <443638A3.1020807@inf.u-szeged.hu>
Ferenc Havasi wrote:
>
> You are right. It was a forgatten code. We removed it with a patch
> commited now.
>
> Thanks!
>
> Ferenc
>
Ferenc, I have just looked at Centralized summary patch. It seems it is
good idea to add check c->mtd->block_isbad against NULL before call in
jffs2_cs_build_filesystem_jeb() function. I understand that your patch
at the moment is for NAND only but someone, for example, may have rootfs
on NOR where block_isbad() method is not provided. Adding that check you
will just get message "...cs_block is not valid..." for JFFS2 at NOR,
otherwise Kernel panic.
.......
int jffs2_cs_build_filesystem_jeb(struct jffs2_sb_info *c)
{
int i, ret;
uint32_t offset;
for (i=0; i < CENT_SUM_RETRY_EMPTY; i++) {
offset = c->blocks[i]->offset;
if(c->mtd->block_isbad) {
if (c->mtd->block_isbad(c->mtd, offset) == 2) {
dbg_cs2("Erase block #%d (offset 0x08%x) is bad! Skip", i, offset);
continue;
}
}
.......
Thanks,
Alexander Belyakov
-------
The content of this message is my personal opinion only and although I
am an employee of Intel, the statements I make here in no way represent
Intel’s position on the issue
**
next prev parent reply other threads:[~2006-04-18 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 13:50 Problem of "JFFS2 summary" phAntOm yAng
2006-04-07 6:28 ` Holger Schurig
2006-04-07 8:12 ` Sascha Hauer
2006-04-07 8:21 ` Alexander Belyakov
2006-04-07 10:02 ` Ferenc Havasi
2006-04-18 8:06 ` Alexander Belyakov [this message]
2006-04-21 1:58 ` Ferenc Havasi
2006-04-21 13:44 ` David Woodhouse
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=44449DFE.6040905@intel.com \
--to=alexander.belyakov@intel.com \
--cc=h.schurig@mn-solutions.de \
--cc=havasi@inf.u-szeged.hu \
--cc=linux-mtd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox