From: giulio fedel <giulio.fedel@andorsystems.com>
To: linux-mtd@lists.infradead.org
Subject: Re: jffs2 kernel dump with 2.6.22-rc7
Date: Fri, 17 Aug 2007 19:14:12 +0200 [thread overview]
Message-ID: <46C5D764.5000303@andorsystems.com> (raw)
In-Reply-To: <8c7950360708011141w3a716a8aua185e9f1931f17e3@mail.gmail.com>
In jffs2_do_unlink() in fs/jffs2/write.c
the jffs2_complete_reservation(c) is called even if
jffs2_reserve_space() is not called. This cause an unmatched
up(&c->alloc_sem) so the locking mechanism does not work.
People using MTD_CAP_NORFLASH flash _and_ CONFIG_JFFS2_SUMMARY do not
see the problem (see os-linux.h for the definition of
jffs2_can_mark_obsolete(c)).
I think this is your problem (it was the mine).
Regards.
Giulio Fedel
--- fs/jffs2/write.c.orig 2007-08-17 19:01:04.000000000 +0200
+++ fs/jffs2/write.c 2007-08-17 19:00:41.000000000 +0200
@@ -549,6 +549,7 @@ int jffs2_do_unlink(struct jffs2_sb_info
/* File it. This will mark the old one obsolete. */
jffs2_add_fd_to_list(c, fd, &dir_f->dents);
up(&dir_f->sem);
+ jffs2_complete_reservation(c);
} else {
struct jffs2_full_dirent **prev = &dir_f->dents;
uint32_t nhash = full_name_hash(name, namelen);
@@ -605,7 +606,6 @@ int jffs2_do_unlink(struct jffs2_sb_info
up(&dead_f->sem);
}
- jffs2_complete_reservation(c);
return 0;
}
next prev parent reply other threads:[~2007-08-17 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8c7950360707091227v14daf14cs48fb1377e903be6c@mail.gmail.com>
2007-08-01 18:41 ` jffs2 kernel dump with 2.6.22-rc7 shanevolpe
2007-08-17 17:14 ` giulio fedel [this message]
2007-08-18 21:08 ` Zac Medico
2007-08-18 21:42 ` Josh Boyer
2007-08-19 0:59 ` Joakim Tjernlund
2007-08-19 8:56 ` David Woodhouse
2007-08-20 3:33 ` Zac Medico
2007-08-20 9:08 ` giulio fedel
2007-07-10 11:09 shanevolpe
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=46C5D764.5000303@andorsystems.com \
--to=giulio.fedel@andorsystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox