From: Artem Bityutskiy <dedekind@infradead.org>
To: kmpark@infradead.org
Cc: 'linux-mtd' <linux-mtd@lists.infradead.org>,
linux-kernel@vger.kernel.org
Subject: RE: Abnormal behavior with JFFS2 on latest kernel
Date: Fri, 15 Feb 2008 11:08:58 +0200 [thread overview]
Message-ID: <1203066538.23414.11.camel@sauron> (raw)
In-Reply-To: <005601c86fb1$7c79f100$1fa9580a@swcenter.sec.samsung.co.kr>
On Fri, 2008-02-15 at 18:02 +0900, Kyungmin Park wrote:
> > On Fri, 2008-02-15 at 16:12 +0900, Kyungmin Park wrote:
> > > 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?
> >
> > Hi Kyungmin,
> >
> > did not look at this, but off the top of my head this might be related
> > to the latest VFS changes (write_begin()/write_end() instead of
> > prepare_write()/commit_write()). Just a hint where you might try to
> > look.
> >
>
> Then can I use the ubifs? I mean ubifs is already changed for latest VFS changes.
> Now I just want to test new driver with latest kernel.
No, in opposite, we have not changed it yet. The old calls were not
removed from VFS and will be kept there for few releases. So we still
use them - this helps to use the same UBIFS sources for older kernels.
But later we'll switch to newer calls which are in fact much better for
UBIFS then the old ones.
But yes, you of course can use UBIFS.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2008-02-15 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 7:12 Abnormal behavior with JFFS2 on latest kernel Kyungmin Park
2008-02-15 8:47 ` Joakim Tjernlund
2008-02-15 8:56 ` Kyungmin Park
2008-02-15 8:59 ` Joakim Tjernlund
2008-02-15 9:35 ` Kyungmin Park
2008-02-15 9:49 ` Joakim Tjernlund
2008-02-15 8:54 ` Artem Bityutskiy
2008-02-15 9:02 ` Kyungmin Park
2008-02-15 9:08 ` Artem Bityutskiy [this message]
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=1203066538.23414.11.camel@sauron \
--to=dedekind@infradead.org \
--cc=kmpark@infradead.org \
--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