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: <4AACD9F1.4000908@redhat.com>
Date:	Sun, 13 Sep 2009 14:39:29 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Valdis.Kletnieks@...edu
CC:	Beth Kon <eak@...ibm.com>, rostedt@...dmis.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Wierdness - linux-next KVM patch breaks Dell Latitude D820, KVM
 not in kernel

On 09/12/2009 11:55 PM, Valdis.Kletnieks@...edu wrote:
> On Wed, 09 Sep 2009 14:59:12 EDT, Valdis.Kletnieks@...edu said:
>
>    
>> So hopefully excluding kvm.git I'll track down the *original* hang...
>>
>> Wish me luck. ;)
>>      
> And luck was not to be had.  Apparently 'git bisect skip' has some bad O(n**2)
> issues - I tried to exclude the kvm.git tree, and it ended up running literally
> overnight with no signs of stopping (see the gory details here:
> https://bugzilla.redhat.com/show_bug.cgi?id=522599 )  Now, I probably *could*
> cobble up something to do the skip as a series of little 20-40 commit skips,
> but that's just getting nuts. ;)
>
> Given that I'm having little luck bisecting this issue in linux-next and
> we're now into the merge window, does anybody have a *better* idea than letting
> the issue get into Linus's tree around -rc1, and hope that bisects more nicely
> than linux-next did, so -rc2 has a fix for it?
>    

Current linux-next should now be easily bisectable without the kvm.git 
issues you encountered.

-- 
error compiling committee.c: too many arguments to function

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