From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: jffs2 Oops on 2.6.10-rc2
Date: Thu, 18 Nov 2004 18:20:46 +0100 [thread overview]
Message-ID: <20041118172046.GB9471@synertronixx3> (raw)
In-Reply-To: <20041118163528.GA9471@synertronixx3>
In nodemgmt.c I remove the following code, which was added after 2.6.9:
#undef KONSTI
#ifdef KONSTI
/* Nodes which have been marked obsolete no longer need to be
associated with any inode. Remove them from the per-inode list */
if (ref->next_in_ino) {
struct jffs2_inode_cache *ic;
struct jffs2_raw_node_ref **p;
ic = jffs2_raw_ref_to_ic(ref);
for (p = &ic->nodes; (*p) != ref; p = &((*p)->next_in_ino))
;
*p = ref->next_in_ino;
ref->next_in_ino = NULL;
}
/* Merge with the next node in the physical list, if there is one
and if it's also obsolete. */
if (ref->next_phys && ref_obsolete(ref->next_phys) ) {
struct jffs2_raw_node_ref *n = ref->next_phys;
ref->__totlen += n->__totlen;
ref->next_phys = n->next_phys;
if (jeb->last_node == n) jeb->last_node = ref;
if (jeb->gc_node == n) {
/* gc will be happy continuing gc on this node */
jeb->gc_node=ref;
}
BUG_ON(n->next_in_ino);
jffs2_free_raw_node_ref(n);
}
/* Also merge with the previous node in the list, if there is one
and that one is obsolete */
if (ref != jeb->first_node ) {
struct jffs2_raw_node_ref *p = jeb->first_node;
while (p->next_phys != ref)
p = p->next_phys;
if (ref_obsolete(p) ) {
p->__totlen += ref->__totlen;
if (jeb->last_node == ref) {
jeb->last_node = p;
}
if (jeb->gc_node == ref) {
/* gc will be happy continuing gc on this node */
jeb->gc_node=p;
}
p->next_phys = ref->next_phys;
jffs2_free_raw_node_ref(ref);
}
}
#endif
That helps, the Kernel doesn't Oops on fresh flashed filesystem. Don't know
if the error is this code or only triggered by it though.
Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
next prev parent reply other threads:[~2004-11-18 17:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 16:35 jffs2 Oops on 2.6.10-rc2 Konstantin Kletschke
2004-11-18 17:20 ` Konstantin Kletschke [this message]
2004-11-20 13:57 ` David Woodhouse
2004-11-20 14:47 ` David Woodhouse
2004-11-20 14:50 ` Konstantin Kletschke
2004-11-20 14:57 ` David Woodhouse
2004-11-20 15:13 ` Artem B. Bityuckiy
2004-11-20 16:28 ` Konstantin Kletschke
2004-11-20 16:31 ` Konstantin Kletschke
2004-11-20 16:35 ` Konstantin Kletschke
2004-11-20 16:34 ` David Woodhouse
2004-11-22 10:27 ` Ian Campbell
2004-11-22 10:50 ` Ian Campbell
2004-11-22 11:05 ` David Woodhouse
2004-11-22 11:42 ` Ian Campbell
2004-11-20 15:12 ` 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=20041118172046.GB9471@synertronixx3 \
--to=lists@ku-gbr.de \
--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