From: Artem Bityutskiy <dedekind@infradead.org>
To: joakim.tjernlund@transmode.se
Cc: linux-mtd@lists.infradead.org,
Adrian Hunter <ext-adrian.hunter@nokia.com>
Subject: Re: [PATCH] [JFFS2] Prevent list corruption when handling write errors
Date: Thu, 29 Mar 2007 12:59:42 +0300 [thread overview]
Message-ID: <1175162382.19966.11.camel@sauron> (raw)
In-Reply-To: <1175161973.2135.1.camel@gentoo-jocke.transmode.se>
On Thu, 2007-03-29 at 11:52 +0200, Joakim Tjernlund wrote:
> On Thu, 2007-03-29 at 11:00 +0300, Adrian Hunter wrote:
> > If a write error occurs, the affected block is placed on the
> > bad_used_list. In the case that the write error occured
> > when writing summary data the block was also being placed on
> > the dirty_list, which caused list corruption and ultimately
> > a soft lockup in jffs2_mark_node_obsolete. This fixes that.
>
> I thougth that node obsoleting was disabled when summary is active?
Of course not. On-flash obsoleting is disabled, but not in-RAM.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2007-03-29 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 8:00 [PATCH] [JFFS2] Prevent list corruption when handling write errors Adrian Hunter
2007-03-29 9:52 ` Joakim Tjernlund
2007-03-29 9:59 ` Artem Bityutskiy [this message]
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=1175162382.19966.11.camel@sauron \
--to=dedekind@infradead.org \
--cc=ext-adrian.hunter@nokia.com \
--cc=joakim.tjernlund@transmode.se \
--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 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.