linux-kernel - Re: [BUG 2.6.30] Bad page map in process

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0907131236320.20647@sister.anvils>
Date:	Mon, 13 Jul 2009 12:56:17 +0100 (BST)
From:	Hugh Dickins <hugh.dickins@...cali.co.uk>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
cc:	Haavard Skinnemoen <haavard.skinnemoen@...el.com>,
	linux-mm@...ck.org, kernel@...32linux.org,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG 2.6.30] Bad page map in process

On Sun, 12 Jul 2009, Guennadi Liakhovetski wrote:
> 
> 2. the specific BUG that I posted originally wasn't very interesting, 
> because it wasn't the first one. Having read a few posts I wasn't quite 
> sure how really severe this BUG was, i.e., whether or not it requiret a 
> reboot. There used to be a message like "reboot is required" around this 
> sort of exceptions, but then it has been removed, so, I thought, it wasn't 
> required any more. But the fact is, that once one such BUG has occurred, 
> new ones will come from various applications and eventually the system 
> will become unusable.

I replaced Bad page state's reboot is needed message by just the BUG
prefix: partly because the bad page handling _is_ now more resilient;
but more because I don't like wasting screenlines which could hold
vital info, and because I didn't see how this BUG differs from others
in whether or not you need a reboot.

A BUG means the kernel is in unknown territory: if you're brave and
want to gather more info, you try to keep on running after a BUG;
if you're cautious, you reboot as soon as possible.

(Hmm, but perhaps I should wire these in to panic_on_oops??)

You did the right thing: kept on running, then decided it wasn't
worth it.  (But you've only sent the one pair of messages gathered:
okay, let's forget the rest until you've sorted the hardware angle.)

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