From: "Kyungmin Park" <kmpark@infradead.org>
To: <joakim.tjernlund@transmode.se>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: RE: Abnormal behavior with JFFS2 on latest kernel
Date: Fri, 15 Feb 2008 17:56:56 +0900 [thread overview]
Message-ID: <005001c86fb0$b9bc6d00$1fa9580a@swcenter.sec.samsung.co.kr> (raw)
In-Reply-To: <1203065237.5419.74.camel@gentoo-jocke.transmode.se>
> > I got following messages.
> > INFO: task pdflush:56 blocked for more than 120 seconds.
> > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> >
> > What are the meanings?
> > Too mush running GC in JFFS2 or others?
> >
> > BR,
> > Kyungmin Park
>
> It is probably erasing lots of blocks and that takes a while, minutes
> some times. I once sent a patch to address this but the patch is racy
> w.r.t module unload. Look in the archive after patches from me.
>
You mean this one?
diff --git a/fs/jffs2/wbuf.c b/fs/jffs2/wbuf.c
index d1d4f27..b2e71c7 100644
--- a/fs/jffs2/wbuf.c
+++ b/fs/jffs2/wbuf.c
@@ -115,7 +115,7 @@ static inline void jffs2_refile_wbuf_blocks(struct jffs2_sb_
D1(printk(KERN_DEBUG "Removing eraseblock at 0x%08x from erasabl
list_del(this);
- if ((jiffies + (n++)) & 127) {
+ if ((jiffies + (n++)) & 127 && !list_empty(&c->erasable_list)) {
/* Most of the time, we just erase it immediately. Other
spend ages scanning it on mount, etc. */
D1(printk(KERN_DEBUG "...and adding to erase_pending_lis
It's already applied, but it's same.
BR,
Kyungmin Park
next parent reply other threads:[~2008-02-15 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <004601c86fa2$201a78d0$1fa9580a@swcenter.sec.samsung.co.kr>
[not found] ` <1203065237.5419.74.camel@gentoo-jocke.transmode.se>
2008-02-15 8:56 ` Kyungmin Park [this message]
2008-02-15 8:59 ` Joakim Tjernlund
2008-02-15 9:35 ` Kyungmin Park
2008-02-15 9:49 ` Joakim Tjernlund
[not found] ` <1203065647.23414.6.camel@sauron>
2008-02-15 9:02 ` Kyungmin Park
2008-02-15 9:08 ` Artem Bityutskiy
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='005001c86fb0$b9bc6d00$1fa9580a@swcenter.sec.samsung.co.kr' \
--to=kmpark@infradead.org \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®