From: David Woodhouse <dwmw2@infradead.org>
To: Adam Wozniak <adam.wozniak@comdev.cc>
Cc: linux-mtd@lists.infradead.org
Subject: Re: different crash (was Re: JFFS2 is crashing the kernel)
Date: Wed, 16 Jan 2002 22:06:27 +0000 [thread overview]
Message-ID: <21352.1011218787@redhat.com> (raw)
In-Reply-To: <3C45F441.B65F5F31@comdev.cc>
adam.wozniak@comdev.cc said:
> Id: build.c,v 1.22 2002/01/09 16:30:57 dwmw2 Exp
Bugger. There was a bug in 1.21 which could cause the symptoms you saw -
but I fixed it in 1.22.
Now I'm confused. It's possible that the shuffling around of code for
portability, although it shouldn't have changed the behaviour in any
significant way, has introduced a bug.
I suspect you have a node or inocache on the list which has been freed and
shouldn't be there.
If this were reproducible, I'd want you to add debugging printks to
jffs2_{alloc,free}_raw_node_ref similar to the ones in the inocache
alloc/free functions. Also to jffs2_raw_ref_to_inum() to print raw and raw->
next_in_ino each time round the loop you identified.
Then boot with debugging (level 1) enabled and log _all_ messages, even the
KERN_DEBUG ones, from the time the filesystem is first mounted.
--
dwmw2
next prev parent reply other threads:[~2002-01-16 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 16:32 JFFS2 is crashing the kernel Sanjay Kumar
2002-01-16 18:22 ` David Woodhouse
2002-01-16 20:02 ` different crash (was Re: JFFS2 is crashing the kernel) Adam Wozniak
2002-01-16 20:32 ` David Woodhouse
2002-01-16 20:35 ` David Woodhouse
2002-01-16 21:44 ` Adam Wozniak
2002-01-16 22:06 ` David Woodhouse [this message]
2002-01-16 22:11 ` Adam Wozniak
2002-01-16 22:20 ` David Woodhouse
2002-01-16 22:04 ` Adam Wozniak
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=21352.1011218787@redhat.com \
--to=dwmw2@infradead.org \
--cc=adam.wozniak@comdev.cc \
--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.