public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Orjan Friberg <of@flatfrog.com>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: CONFIG_PREEMPT and JFFS2 oops
Date: Thu, 26 Jan 2012 10:26:20 +0100	[thread overview]
Message-ID: <4F211C3C.3090004@flatfrog.com> (raw)
In-Reply-To: <4F206DCE.3060609@flatfrog.com>

On 01/25/2012 10:02 PM, Orjan Friberg wrote:
> That one-liner was boiled down from the following program, which still
> oopses instantly:

The C program seems to work fine with CONFIG_PREEMPT_NONE=y.

If that is indeed the problem I guess it's reasonable that it worked
better with PREEMPT_VOLUNTARY than PREEMPT because there are fewer
preemtion points.

-- 
Orjan Friberg
FlatFrog Laboratories AB

  reply	other threads:[~2012-01-26  9:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 20:12 CONFIG_PREEMPT and JFFS2 oops Orjan Friberg
2012-01-25 21:02 ` Orjan Friberg
2012-01-26  9:26   ` Orjan Friberg [this message]
2012-01-25 21:18 ` Paul Walmsley
2012-01-25 21:18   ` Paul Walmsley
2012-01-26  3:44     ` Paul Walmsley
2012-01-26 10:15   ` Orjan Friberg
2012-01-26 11:19     ` Joakim Tjernlund
2012-01-26 11:54     ` Orjan Friberg
2012-01-26 16:09       ` Paul Walmsley
2012-01-26 16:28         ` Joakim Tjernlund
2012-01-26 16:35           ` Paul Walmsley
2012-01-26 16:38             ` Paul Walmsley
2012-01-26 16:48               ` Joakim Tjernlund
2012-01-26 16:57                 ` Paul Walmsley
2012-01-26 17:33                   ` Joakim Tjernlund
2012-01-26 20:01                     ` Joakim Tjernlund
2012-01-28  9:51                       ` Paul Walmsley
2012-01-28 14:42                         ` Joakim Tjernlund
2012-01-28  9:50                     ` Paul Walmsley
2012-01-26 17:54                   ` Orjan Friberg
2012-01-26 16:37         ` Orjan Friberg
2012-01-26 16:43           ` Paul Walmsley

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=4F211C3C.3090004@flatfrog.com \
    --to=of@flatfrog.com \
    --cc=linux-omap@vger.kernel.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