linux-kernel - Re: linux-next: Tree for July 18 (very early crash on x86

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: <200807191731.08172.bzolnier@gmail.com>
Date:	Sat, 19 Jul 2008 17:31:07 +0200
From:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Dave Hansen <haveblue@...ibm.com>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: linux-next: Tree for July 18 (very early crash on x86_32)

Hi,

Since around next-20080709 linux-next has been crashing very early in
the boot on my x86_32 laptop (the problem is also reproducible under
qemu, config & screenshot attached).  Now that merging has paused for
a moment I took a closer look into the issue.

First I bisected it down to commit 99c2fcc5306153c8ae56542b3e80dddaf77baa45
("Merge branch 'quilt/driver-core'") and then with a little patchwork I
identified the source as a commit 0e3638d1e04040121af00195f7e4628078246489
("warn when statically-allocated kobjects are used").

With commit 0e3638d1e04040121af00195f7e4628078246489 reverted and fixup
from Al for vfs-next/net-next conflict (http://lkml.org/lkml/2008/7/18/591)
next-20080718 works fine for me.

BTW ide tree's conflicts against Linus' tree should be fixed now.

Thanks,
Bart

Download attachment "bug.png" of type "image/png" (22881 bytes)

View attachment "bug.config" of type "text/plain" (57240 bytes)