All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Joel Reardon <joel@clambassador.com>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: mtdchar kernel oops
Date: Wed, 18 Apr 2012 21:51:21 -0300	[thread overview]
Message-ID: <CAOMZO5Cc0hWobNW4y-Di7F3D_LHS1cj+c4w-gNaK9t2NxKpE3A@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5BL8bKauB6-srbZCLapHJNAVRqB0g0uw+17_h1wy3_9-g@mail.gmail.com>

On Sun, Apr 15, 2012 at 11:19 AM, Fabio Estevam <festevam@gmail.com> wrote:
> On Sun, Apr 15, 2012 at 8:58 AM, Joel Reardon <joel@clambassador.com> wrote:
>> I think that this patch:
>> "mtdchar: kill persistently held vfsmount"
>> http://permalink.gmane.org/gmane.linux.kernel.commits.head/314175
>>
>> has started causing kernel oops's when running ubiformat. The oops is
>> occuring in fs/namespace.c's mnt_add_count() line:
>>        this_cpu_add(mnt->mnt_pcp->mnt_count, n);
>
> I also see kernel oops when running flash_eraseall on a SPI NOR flash.
>
> If this patch is reverted the flash_eraseall operation is successful.

I am no longer getting kernel oops on 3.4.0-rc3-next-20120418.

WARNING: multiple messages have this Message-ID (diff)
From: Fabio Estevam <festevam@gmail.com>
To: Joel Reardon <joel@clambassador.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: mtdchar kernel oops
Date: Wed, 18 Apr 2012 21:51:21 -0300	[thread overview]
Message-ID: <CAOMZO5Cc0hWobNW4y-Di7F3D_LHS1cj+c4w-gNaK9t2NxKpE3A@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5BL8bKauB6-srbZCLapHJNAVRqB0g0uw+17_h1wy3_9-g@mail.gmail.com>

On Sun, Apr 15, 2012 at 11:19 AM, Fabio Estevam <festevam@gmail.com> wrote:
> On Sun, Apr 15, 2012 at 8:58 AM, Joel Reardon <joel@clambassador.com> wrote:
>> I think that this patch:
>> "mtdchar: kill persistently held vfsmount"
>> http://permalink.gmane.org/gmane.linux.kernel.commits.head/314175
>>
>> has started causing kernel oops's when running ubiformat. The oops is
>> occuring in fs/namespace.c's mnt_add_count() line:
>>        this_cpu_add(mnt->mnt_pcp->mnt_count, n);
>
> I also see kernel oops when running flash_eraseall on a SPI NOR flash.
>
> If this patch is reverted the flash_eraseall operation is successful.

I am no longer getting kernel oops on 3.4.0-rc3-next-20120418.

  reply	other threads:[~2012-04-19  0:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 11:58 mtdchar kernel oops Joel Reardon
2012-04-15 14:19 ` Fabio Estevam
2012-04-15 14:19   ` Fabio Estevam
2012-04-19  0:51   ` Fabio Estevam [this message]
2012-04-19  0:51     ` Fabio Estevam
2012-04-15 14:28 ` Richard Weinberger
2012-04-15 14:34   ` Fabio Estevam
2012-04-15 15:32 ` Al Viro
2012-04-15 15:32   ` Al Viro
2012-04-15 17:57   ` Joel Reardon
2012-04-15 17:57     ` Joel Reardon
2012-04-15 21:53     ` Al Viro
2012-04-15 21:53       ` Al Viro
2012-04-16 12:37       ` Joel Reardon
2012-04-16 12:37         ` Joel Reardon
2012-04-16 19:17         ` Al Viro
2012-04-16 19:17           ` Al Viro
2012-04-18 12:55           ` Joel Reardon
2012-04-18 12:55             ` Joel Reardon
2012-04-18 13:12             ` Artem Bityutskiy
2012-04-18 13:12               ` Artem Bityutskiy

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=CAOMZO5Cc0hWobNW4y-Di7F3D_LHS1cj+c4w-gNaK9t2NxKpE3A@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=joel@clambassador.com \
    --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 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.