From: James Morris <jmorris@namei.org>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jonathan Cameron <jic23@cam.ac.uk>,
David Howells <dhowells@redhat.com>,
linux-mtd@lists.infradead.org
Subject: Re: [regression] jffs2 gc thread oops in set_dumpable()
Date: Sat, 10 Jan 2009 00:38:38 +1100 (EST) [thread overview]
Message-ID: <alpine.LRH.1.10.0901100038100.24230@tundra.namei.org> (raw)
In-Reply-To: <20090109142148.35f3a99a@hskinnemoen-d830>
On Fri, 9 Jan 2009, Haavard Skinnemoen wrote:
> Hi all,
>
> The following crash has been observed on an ARM platform (intelmote 2)
> and an AVR32 platform (ATSTK1006). In both cases, it's a NULL pointer
> dereference at virtual address 0x150 from set_dumpable() called from
> one of the jffs2_gcd_mtdX threads, and both boards work fine with
> 2.6.28.
This patch should fix it:
http://marc.info/?l=linux-kernel&m=123141356005033&w=2
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2009-01-09 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 13:21 Haavard Skinnemoen
2009-01-09 13:38 ` James Morris [this message]
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=alpine.LRH.1.10.0901100038100.24230@tundra.namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=haavard.skinnemoen@atmel.com \
--cc=jic23@cam.ac.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®