linux-kernel - Re: [-next Jan 18] Boot failure on s390 with DEVTMPFS=y

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ac3eb2511001180631r5209dff6s83ecdaee708e0b0b@mail.gmail.com>
Date:	Mon, 18 Jan 2010 15:31:09 +0100
From:	Kay Sievers <kay.sievers@...y.org>
To:	Sachin Sant <sachinp@...ibm.com>
Cc:	Greg KH <greg@...ah.com>, Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	linux-s390@...r.kernel.org
Subject: Re: [-next Jan 18] Boot failure on s390 with DEVTMPFS=y

On Mon, Jan 18, 2010 at 15:21, Sachin Sant <sachinp@...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.

Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/