From: "Joakim Tjernlund" <Joakim.Tjernlund@transmode.se>
To: "'Jean Pihet'" <jpihet@mvista.com>, <linux-mtd@lists.infradead.org>
Cc: nickpiggin@yahoo.com.au, joern@logfs.org, dwmw2@infradead.org,
'Alexey Korolev' <akorolev@infradead.org>,
akpm@linux-foundation.org
Subject: RE: [BUG] JFFS2 usage of write_begin and write_end functions causes kernel panic
Date: Thu, 10 Apr 2008 20:35:07 +0200 [thread overview]
Message-ID: <018a01c89b39$9a2b4fb0$ce81ef10$@Tjernlund@transmode.se> (raw)
In-Reply-To: <200804101918.21362.jpihet@mvista.com>
> -----Original Message-----
> From: linux-mtd-bounces@lists.infradead.org [mailto:linux-mtd-bounces@lists.infradead.org] On Behalf
> Of Jean Pihet
> Sent: den 10 april 2008 19:18
> To: linux-mtd@lists.infradead.org
> Cc: nickpiggin@yahoo.com.au; joern@logfs.org; dwmw2@infradead.org; Alexey Korolev; akpm@linux-
> foundation.org
> Subject: Re: [BUG] JFFS2 usage of write_begin and write_end functions causes kernel panic
>
> Alexey,
>
> Here is the patch (attached) I applied to get a stable JFFS2 filesystem.
> The changes have been cherry picked from
> http://sourceforge.net/projects/mtd-mods.
>
> I stressed it with intensive read/write, flash fill-up and data removal. A few
> GB's of data have been transferred without any problem. I didn't try the tool
> you mentionned though.
> Tested on OMAP3 platform.
>
> Now I am testing with PREEMPT_RT config.
Is this in Linus tree too?
Jocke
next prev parent reply other threads:[~2008-04-10 18:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 16:53 [BUG] JFFS2 usage of write_begin and write_end functions causes kernel panic Alexey Korolev
2008-04-10 17:18 ` Jean Pihet
2008-04-10 18:35 ` Joakim Tjernlund [this message]
2008-04-10 18:51 ` Jean Pihet
2008-04-10 18:56 ` Joakim Tjernlund
2008-04-11 18:00 ` Alexey Korolev
2008-04-11 18:05 ` Artem Bityutskiy
2008-04-13 10:50 ` Jörn Engel
2008-04-13 12:42 ` David Woodhouse
2008-04-14 8:25 ` Alexander Belyakov
2008-04-12 13:31 ` Joakim Tjernlund
2008-04-12 14:48 ` David Woodhouse
2008-04-14 16:09 ` Alexey Korolev
2008-04-14 17:08 ` Alexey Korolev
2008-04-24 21:10 ` Anders Grafström
2008-04-24 22:15 ` David Woodhouse
2008-04-25 10:04 ` Alexey Korolev
2008-04-25 16:09 ` Anders Grafström
2008-04-26 14:52 ` David Woodhouse
2008-04-28 20:00 ` Anders Grafström
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='018a01c89b39$9a2b4fb0$ce81ef10$@Tjernlund@transmode.se' \
--to=joakim.tjernlund@transmode.se \
--cc=akorolev@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=jpihet@mvista.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nickpiggin@yahoo.com.au \
/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.