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: <20090103181333.GA19413@elte.hu>
Date:	Sat, 3 Jan 2009 19:13:33 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Mike Travis <travis@....com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PULL] cpumask tree


* Ingo Molnar <mingo@...e.hu> wrote:

> Also, while bisecting this window of commits i found that neither would 
> build successfully due to a typo - and the typo is fixed in 095fb96. So 
> since we rebase this portion anyway due to excessive amount of bugs, 
> i'll make it fully bisectable by rebasing right at 095fb96, backmerge 
> the fixlet from eeff031 and redo the whole series dropping the two bad 
> patches. Since this portion of the tree has no appreciable testing value 
> the rebase is the right thing to do here.

okay, i've done this now and pushed out the resulting tree to 
tip/cpus4096-v2. It is a no-content-changed reshuffle of the tail ~10 
commits of tip/cpus4096:

 $ git diff cpus4096..cpus4096-v2
 $

i dropped the two broken patches i bisected today, and backmerged a fixlet 
to make it more bisectable, and reordered fixes next to the merge point - 
and the new changes now come after that.

this finally is something that has no known regressions and looks pushable 
to Linus. I've started the -tip tests, lets see how well this holds up 
now.

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