linux-kernel - Re: BSOD

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]

Date:	Mon, 19 Mar 2007 13:05:44 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jesse.barnes@...el.com
Cc:	zaitcev@...hat.com, jg@...top.org, linux-kernel@...r.kernel.org
Subject: Re: BSOD

From: Jesse Barnes <jesse.barnes@...el.com>
Date: Mon, 19 Mar 2007 12:54:36 -0700

> Kernel based modesetting should get us a lot of things:

But for panics you're ignoring what Peter and I are saying.

Mode setting is complex and it is not going to work exactly when you
need the kernel crash message the most.

After debugging the kernel for 10+ years I can tell you one thing, for
a bad crash what's going to happen is you'll get the printk but that's
about all that will work at that point, and the kernel is going to
hang next.  Sometimes you won't get the whole panic message, just
the beginning, even with the most simplistic printk implementation.

You will not, I repeat, will not be able to mode switch or anything
non-trivial like that when the kernel is in this state.

Mode switching on panic, just say no. :-)

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