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: Wed, 25 Jan 2012 22:02:06 +0100	[thread overview]
Message-ID: <4F206DCE.3060609@flatfrog.com> (raw)
In-Reply-To: <4F206213.9070704@flatfrog.com>

On 01/25/2012 09:12 PM, Orjan Friberg wrote:
> I've boiled it down to whether CONFIG_PREEMPT (bug happens) or
> CONFIG_PREEMPT_VOLUNTARY (bug doesn't happen) is selected.

No, I haven't.  The problem disappeared only for

    while :; do dd if=/dev/zero of=file bs=800 count=1; done

That one-liner was boiled down from the following program, which still
oopses instantly:

    #include <stdio.h>
    #include <unistd.h>
    #include <sys/types.h>
    #include <sys/stat.h>
    #include <fcntl.h>

    int main()
    {
      int fd;
      struct stat st;
      char buf[800];

      do {
        unlink("file2");
        fd = open("file1", O_RDWR|O_CREAT|O_TRUNC, 0666);
        stat("file1", &st);
        lseek(fd, 0, SEEK_SET);
        write(fd, buf, 800);
        close(fd);
        rename("file1", "file2");
      } while (1);

      return 0;
    }


(Apologies for spamming.)


-- 
Orjan Friberg
FlatFrog Laboratories AB

  reply	other threads:[~2012-01-25 21:02 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 [this message]
2012-01-26  9:26   ` Orjan Friberg
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=4F206DCE.3060609@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