linux-kernel - Re: -next March 3: Boot failure on x86 (Oops)

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: <4B90A031.8090306@kernel.org>
Date:	Fri, 05 Mar 2010 15:09:53 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Sachin Sant <sachinp@...ibm.com>
CC:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: -next March 3: Boot failure on x86 (Oops)

On 03/05/2010 03:08 PM, Tejun Heo wrote:
> Hmmm... this means that on one of the chunks, chunk->list.next was
> NULL (BTW, the disassembly is from unlinked object, right?).  The main
> allocation code hasn't seen much change lately.  The only changes are,
> 
> 22b737f4c75197372d64afc6ed1bccd58c00e549 : just refactoring
> 833af8427be4b217b5bc522f61afdbd3f1d282c2 : possible but isn't very new

Can you also please try reverting the above two commits?

Thanks.

-- 
tejun
--
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/