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: <alpine.LFD.2.00.0911231034090.24119@localhost.localdomain>
Date:	Mon, 23 Nov 2009 10:45:47 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	indexer <indexer@...ernode.on.net>
cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>,
	Feng Tang <feng.tang@...el.com>,
	bugzilla-daemon@...zilla.kernel.org
Subject: Re: [Bug 14658] Regression in efi.c

On Mon, 23 Nov 2009, indexer wrote:
> > while the bisect should have be done with
> > 
> > good 2.6.30
> > bad  2.6.31
> > 
> > William, could you please go through the bisect pain again?
>> 
> I had already done a similar bisect to this in private conversation to Huang
> Ying, and is what prompted me to expand my bisect out. I redid it regardless
> and will send you the information.
> 
> commit 74fca6a42863ffacaf7ba6f1936a9f228950f657
> Author: Linus Torvalds <torvalds@...ux-foundation.org>
> Date:   Wed Sep 9 15:13:59 2009 -0700
> 
>    Linux 2.6.31
> 
> Makefile |    2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)

So you are saying that 
 
> # good: [7135a71b19be1faf48b7148d77844d03bc0717d6] aoe: allocate unused
> request_queue for sysfs
> git bisect good 7135a71b19be1faf48b7148d77844d03bc0717d6

which is the last code changing commit before the 2.6.31 release is
booting fine, but with the release commit which merily changes the
Makefile it is not ?

> PS - The fact remains i still cant efi boot in 2.6.32-rc7, so this bug still
> exists, and I will keep doing what i can to help track this down.

Sure, but I hope we agree that it does not make much sense to search
2.6.31..now when we already know that 2.6.31 is not booting and the
change which causes the problem is between 2.6.30 and 2.6.31.

Thanks,

	tglx

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