From: Thomas Gleixner <tglx@linutronix.de>
To: Robert Liu <robertliu@wiscore.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: do R/W tests on JFFS2 and suffer segmentation fault
Date: Tue, 21 Feb 2006 10:25:14 +0100 [thread overview]
Message-ID: <1140513914.2480.861.camel@localhost.localdomain> (raw)
In-Reply-To: <43FA6A26.8000005@wiscore.com>
On Tue, 2006-02-21 at 09:17 +0800, Robert Liu wrote:
> I am doing some read/write tests on JFFS2 partition, and find there may be
> a bug in jffs2_remove_from_hash_table().
Which kernel version ? Any patches related to MTD/JFFS2 applied ?
> Tests sometimes failed with segmentation fault.
> I set the JFFS2 debug level to 1, and add several debug infomation in
> jffs2_remove_from_hash_table().
> It seems jffs2 try to remove an entry with prev is 0x200200 and next is
> 0x100100.
Thats the list_head poison code (see include/linux/list.h
LIST_POISON1/2). The entry was removed before.
tglx
next prev parent reply other threads:[~2006-02-21 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 1:17 do R/W tests on JFFS2 and suffer segmentation fault Robert Liu
2006-02-21 9:25 ` Thomas Gleixner [this message]
2006-02-21 9:54 ` Robert Liu
2006-02-24 4:47 ` Robert Liu
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=1140513914.2480.861.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=robertliu@wiscore.com \
/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