From: David Woodhouse <dwmw2@infradead.org>
To: Estelle HAMMACHE <estelle.hammache@st.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 & NAND failure
Date: Sat, 20 Nov 2004 18:57:29 +0000 [thread overview]
Message-ID: <1100977049.7949.36.camel@localhost.localdomain> (raw)
In-Reply-To: <419E1DE0.FDD5DEC0@st.com>
On Fri, 2004-11-19 at 17:22 +0100, Estelle HAMMACHE wrote:
> I feel that writing wbuf immediately adds code without necessity
> (or maybe I'm just too lazy to test it).
The code is there already; it's just a case of making it use wbuf
instead of buf. That shouldn't be so hard.
> Maybe I ought to test nextblock == 0 in addition to the
> obsolete flag to make the exclusion case more precise in
> jffs2_add_physical_node_ref ?
Ah, OK. Yes, that might be appropriate.
> Or is the "dirty" node really necessary ? what happens if we
> don't list it in the raw node refs ?
We'll try writing to that same offset again, and will fail.
--
dwmw2
next prev parent reply other threads:[~2004-11-20 18:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 17:15 JFFS2 & NAND failure Estelle HAMMACHE
2004-11-18 16:27 ` David Woodhouse
2004-11-18 17:54 ` Estelle HAMMACHE
2004-11-19 13:17 ` David Woodhouse
2004-11-19 16:22 ` Estelle HAMMACHE
2004-11-20 18:57 ` David Woodhouse [this message]
2004-11-20 19:19 ` David Woodhouse
2004-11-20 22:13 ` David Woodhouse
2004-12-09 14:57 ` David Woodhouse
2004-12-09 17:06 ` Estelle HAMMACHE
2004-12-15 12:33 ` Estelle HAMMACHE
2005-02-02 16:21 ` Estelle HAMMACHE
2005-04-04 12:58 ` Artem B. Bityuckiy
2005-04-04 13:58 ` Estelle HAMMACHE
2005-04-04 14:47 ` Artem B. Bityuckiy
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=1100977049.7949.36.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=estelle.hammache@st.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