From: Adam Wozniak <adam.wozniak@comdev.cc>
To: gleixner@autronix.de
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org, jffs-dev@axis.com
Subject: Re: JFFS2 list_dirty corruption
Date: Wed, 20 Feb 2002 15:55:17 -0800 [thread overview]
Message-ID: <3C743765.F0A5F5D8@comdev.cc> (raw)
In-Reply-To: 02022021101508.18560@thomas
Thomas Gleixner wrote:
>
> On Wednesday, 20. February 2002 20:41, Thomas Gleixner wrote:
> > While hacking on JFFS2 for NAND I found a possibility, where scan_medium
> > corrupts list_dirty.
> This patch resolves the problem:
>
> --- org/fs/jffs2/scan.c
> +++ work/fs/jffs2/scan.c
> @@ -128,9 +128,15 @@
> (!c->nextblock || c->nextblock->free_size <
> jeb->free_size)) {
> /* Better candidate for the next writes to
> go to */
> if (c->nextblock)
> + /* We must delete, because mark_node_obsolete
> + could have added this block to dirty_list already */
> + list_del(&c->nextblock->list);
> list_add(&c->nextblock->list,
> &c->dirty_list);
> c->nextblock = jeb;
> } else {
> + /* We must delete, because mark_node_obsolete
> + could have added this block to dirty_list already */
> + list_del(&jeb->list);
> list_add(&jeb->list, &c->dirty_list);
> }
> } else {
>
> I put it into CVS too
Ummm. Applying that patch gives me a seg fault on boot.
--Adam
--
Adam Wozniak (KG6GZR) COM DEV Wireless - Digital and Software Systems
awozniak@comdev.cc 805 Aerovista Place, San Luis Obispo, CA 93401
http://www.comdev.cc
Voice: (805) 544-1089 Fax: (805) 544-2055
next prev parent reply other threads:[~2002-02-20 23:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 19:41 JFFS2 list_dirty corruption Thomas Gleixner
2002-02-20 20:10 ` Thomas Gleixner
2002-02-20 23:55 ` Adam Wozniak [this message]
2002-02-20 23:58 ` Adam Wozniak
2002-02-21 0:26 ` Thomas Gleixner
2002-02-21 8:59 ` David Woodhouse
2002-02-21 9:19 ` Thomas Gleixner
2002-02-21 9:23 ` 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=3C743765.F0A5F5D8@comdev.cc \
--to=adam.wozniak@comdev.cc \
--cc=dwmw2@infradead.org \
--cc=gleixner@autronix.de \
--cc=jffs-dev@axis.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 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.