From: Orjan Friberg <of@flatfrog.com>
To: <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 oops when writing to two partitions simultaneously
Date: Wed, 25 Jan 2012 20:53:30 +0100 [thread overview]
Message-ID: <4F205DBA.2090103@flatfrog.com> (raw)
In-Reply-To: <4F1F004C.6040501@flatfrog.com>
On 01/24/2012 08:02 PM, Orjan Friberg wrote:
> I'll be trying out various kernel versions next.
I've boiled it down to whether CONFIG_PREEMPT (bug happens) or
CONFIG_PREEMPT_VOLUNTARY (bug doesn't happen) is selected. Of course,
changing that affects a other things like inline spinlocking.
By changing this option, I've made the bug go away in a 2.6.32 and
2.6.37 setup where it previously happened, and I've made it appear in a
2.6.39 setup where it previously didn't happen.
I'll be posting this on linux-omap mailing list too. I don't have any
other architecture to try this on, and I'm aware that the problem may
lie in arch-dependent code (spinlock implementation?).
--
Orjan Friberg
FlatFrog Laboratories AB
next prev parent reply other threads:[~2012-01-25 19:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 9:55 JFFS2 oops when writing to two partitions simultaneously Orjan Friberg
2012-01-24 17:15 ` Orjan Friberg
2012-01-24 19:02 ` Orjan Friberg
2012-01-25 19:53 ` Orjan Friberg [this message]
2012-01-25 21:01 ` Orjan Friberg
2012-01-26 8:19 ` Joakim Tjernlund
2012-01-26 9:02 ` Orjan Friberg
2012-01-26 9:53 ` Joakim Tjernlund
2012-01-26 9:02 ` Orjan Friberg
2012-01-26 11:53 ` Joakim Tjernlund
2012-01-26 12:51 ` Orjan Friberg
2012-01-26 13:16 ` Joakim Tjernlund
2012-01-26 14:07 ` Orjan Friberg
2012-01-26 14:23 ` Joakim Tjernlund
2012-01-26 14:53 ` Orjan Friberg
2012-01-26 15:17 ` Joakim Tjernlund
2012-01-26 15:25 ` Orjan Friberg
2012-01-26 16:05 ` Orjan Friberg
2012-01-26 16:17 ` Joakim Tjernlund
2012-01-26 14:52 ` Joakim Tjernlund
2012-01-26 15:09 ` Joakim Tjernlund
2012-01-26 15:18 ` Orjan Friberg
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=4F205DBA.2090103@flatfrog.com \
--to=of@flatfrog.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 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.