linux-kernel - Re: Shutdown and Reboot Regression 2.6.25-rc[78]

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:	Sat, 12 Apr 2008 09:04:11 +0200
From:	Bongani Hlope <bonganilinux@...b.co.za>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Shutdown and Reboot Regression 2.6.25-rc[78]

On Saturday 12 April 2008 01:12:37 Linus Torvalds wrote:
> On Fri, 11 Apr 2008, Bongani Hlope wrote:
> > After about 4 restarts and 4 reboots, 2.6.25-rc9 seems to work fine with
> > and without the revert. I'll do some more testing.  The assembly output
> > files for kernel/printk.c don't seem that different between rc9 and rc7.
> > I'll see what else I can test.
>
> Ok, I suspect it may be timing-dependent and slightly random.
>

Nope it happens all the time with rc7 and rc8.... 

> Sadly, that is absolutely the case where "git bisect" works the worst. The
> end result of bisection will basically be _totally_ random if even one of
> the "git bisect bad/good" choises were wrong - doing a binary search is
> a very efficient way to find the buggy commit, but it also means that a
> single wrong turn will efficiently find a commit that is somewhere totally
> different.
>

git revert 266c2e0abeca649fa6667a1a427ad1da507c6375 on rc8 makes rc8 work 
again.

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