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: <20140610191943.GA19896@sucs.org>
Date:	Tue, 10 Jun 2014 20:19:43 +0100
From:	Sitsofe Wheeler <sitsofe@...il.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Igor Mammedov <imammedo@...hat.com>,
	Toshi Kani <toshi.kani@...com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [BISECTED][REGRESSION] Kernel does not boot on EeePC

On Mon, Jun 09, 2014 at 04:02:15PM +0200, Ingo Molnar wrote:
> 
> * H. Peter Anvin <hpa@...or.com> wrote:
> 
> > I really want to say *THANK YOU* to Sitsofe for a very timely and 
> > complete report.  You really saved us some highly valuable time.
> 
> Seconded!

You're welcome. For what it's worth these are the things that allowed
this drive-by testing to occur:

git bisect:
Without this there would have been a generic complaint that would have
only gone to the general kernel mailing list. I thought the issue was
going to lie with the GPU drivers but just following the bisection and
testing the final commit zoned in on the true cause.

Able to cut out most features:
I tend to build cut down kernels which only supports my hardware because
they take less time to compile and boot faster.

Single file builds:
I often do builds on Internet connected machines. Because I can 
can build everything in I only have one file to copy at the end.

Distro doesn't need initrd/initramfs:
One less thing to setup because everything is built in but some distros
seem dependent on having one these days.

I guess the one nice thing to have in the future would be a make
checkedconfig that automatically turned on all checking/verification
features (e.g. slab debugging/memory poisoning) for the current config.
This is would make it easier to get such kernels 

-- 
Sitsofe | http://sucs.org/~sits/
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ