From: Thomas Gleixner <tglx@linutronix.de>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org,
Sergei Sharonov <Sergei.Sharonov@Halliburton.com>
Subject: Re: failed write verify causes segmentation fault
Date: Wed, 16 Mar 2005 20:51:16 +0100 [thread overview]
Message-ID: <1111002676.4814.112.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <1110974906.30606.38.camel@sauron.oktetlabs.ru>
On Wed, 2005-03-16 at 15:08 +0300, Artem B. Bityuckiy wrote:
> This is only one possible reason. The other possible reason which I
> think is more likely has happened in your case is that JFFS2 tried to
> write to a non-empty NAND page, e.g., the page didn't contain all 0xFF.
> In this case write_verify() might fail as well. I don't know why JFFS2
> might do that, possibly there is some bug.
The question is not why the write verify fails. In his test environment
a page failure is expected to happen at some point. The question is why
JFFS2 did not cope with the problem as it is supposed to be.
tglx
next prev parent reply other threads:[~2005-03-16 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 1:09 failed write verify causes segmentation fault Sergei Sharonov
2005-03-16 12:08 ` Artem B. Bityuckiy
2005-03-16 19:36 ` Thomas Gleixner
2005-03-16 19:51 ` Thomas Gleixner [this message]
2005-03-17 18:20 ` Sergei Sharonov
2005-03-16 19:53 ` Thomas Gleixner
2005-03-16 21:44 ` Thomas Gleixner
2005-03-17 15:29 ` Sergei Sharonov
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=1111002676.4814.112.camel@tglx.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=Sergei.Sharonov@Halliburton.com \
--cc=dedekind@infradead.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