linux-kernel - Re: [x86] BUG: unable to handle kernel NULL pointer dereference at (null)

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: <CA+55aFzQC=W010GTxjXjBnsKO0CycXe7VZB+LTiNNtuBug_rbw@mail.gmail.com>
Date:	Tue, 8 Oct 2013 10:31:57 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Richard Henderson <rth@...ddle.net>,
	Jakub Jelinek <jakub@...hat.com>,
	Oleg Nesterov <oleg@...hat.com>
Subject: Re: [x86] BUG: unable to handle kernel NULL pointer dereference at (null)

On Tue, Oct 8, 2013 at 10:15 AM, Fengguang Wu <fengguang.wu@...el.com> wrote:
>
> [   27.865982] Kernel BUG at c10563af [verbose debug info unavailable]

Ugh, you've turned off DEBUG_BUGVERBOSE.

We probably shouldn't even allow that. The space savings aren't worth the pain.

I'm not seeing the pattern in your oopses, there's at least three
different cases. At a guess, it's some lock - or a memory allocator -
that is broken by the bitop breakage, and then the oopses are just
fallout from that..

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