From: Greg KH <greg@kroah.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Sachin Sant <sachinp@in.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [-next Jan 18] Boot failure on s390 with DEVTMPFS=y
Date: Tue, 19 Jan 2010 13:14:22 -0800 [thread overview]
Message-ID: <20100119211422.GA10319@kroah.com> (raw)
In-Reply-To: <ac3eb2511001180631r5209dff6s83ecdaee708e0b0b@mail.gmail.com>
On Mon, Jan 18, 2010 at 03:31:09PM +0100, Kay Sievers wrote:
> On Mon, Jan 18, 2010 at 15:21, Sachin Sant <sachinp@in.ibm.com> wrote:
> > Today next (next-20100118) failed to boot on a s390 box
> > with the following Oops :
>
> > Unable to handle kernel pointer dereference at virtual kernel address
> > 0000000000543000
>
> > <00000000001eb5da> shmem_fill_super+0x13a/0x25c
> > <0000000000228cfa> get_sb_single+0xbe/0xdc
> > <000000000034ffc0> dev_get_sb+0x2c/0x38
> > <000000000066c602> devtmpfs_init+0x46/0xc0
>
> > Previous next builds worked fine on the same box. The only difference
> > between configs of the two builds was CONFIG_DEVTMPFS. This option was
> > enabled while compiling 20100118.
>
> Heiko Carstens posted a simple patch to work around the issue that
> s390 write-protects the string, the option parser tries to modify.
> When Greg has pick it up, this should be fixed.
Yes, I've now queued it up in my trees.
thanks,
greg k-h
next prev parent reply other threads:[~2010-01-19 21:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 8:57 linux-next: Tree for January 18 Stephen Rothwell
2010-01-18 14:21 ` [-next Jan 18] Boot failure on s390 with DEVTMPFS=y Sachin Sant
2010-01-18 14:31 ` Kay Sievers
2010-01-19 21:14 ` Greg KH [this message]
2010-01-19 23:49 ` Stephen Rothwell
2010-01-18 23:44 ` linux-next: Tree for January 18 (pci + pm) Randy Dunlap
2010-01-19 23:04 ` Rafael J. Wysocki
2010-01-20 4:39 ` Jesse Barnes
2010-01-20 5:20 ` Stephen Rothwell
2010-01-20 16:53 ` Randy Dunlap
2010-01-28 16:33 ` Randy Dunlap
2010-01-28 19:04 ` Jesse Barnes
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=20100119211422.GA10319@kroah.com \
--to=greg@kroah.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sachinp@in.ibm.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).