linux-kernel - Re: Bisected regression

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:	Thu, 10 Dec 2009 11:34:45 -0800
From:	Roland Dreier <rdreier@...co.com>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Yinghai Lu <yinghai@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Bisected regression

 > Roland, are you filing a report for this?

Yes, I'll try to track this down.

 > I can test other patches if you have good ideas, otherwise I suggest we
 > revert the commit.

I'll definitely try to get the BIOS fixed but I do also think that the
kernel shouldn't panic on bad info from the BIOS -- we used to be able
to run fine with what the BIOS gave us.  BIOSes are always going to be
crap, and we can print nasty messages in those cases, but the kernel
shouldn't panic unless things are really hopeless.

The benefit of the commit in question seemed to be code cleanup and
reducing use of bootmem -- which I don't think is enough benefit to
justify increasing fragility at runtime.

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