linux-kernel - Re: [bug #2] Re: [PATCH 00/35] cpumask: Replace cpumask

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:	Thu, 23 Oct 2008 18:09:59 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Mike Travis <travis@....com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [bug #2] Re: [PATCH 00/35] cpumask: Replace cpumask_t with
	struct cpumask


* Mike Travis <travis@....com> wrote:

> Rusty Russell wrote:
> > On Friday 24 October 2008 01:20:25 Ingo Molnar wrote:
> >> Thomas has started a -tip cross-build test, and there's massive
> >> cross-build failures as well due to the cpumask changes:
> > 
> > Yes.  linux-next reported the same thing.  I've backed out various arch 
> > changes for this reason.
> > 
> >> it seems to me that this commit is massively borked:
> >>
> >>   4a792c2: cpumask: make CONFIG_NR_CPUS always valid
> > 
> > Yep.  This is the big one I dropped.  There are a few others; Mike is just 
> > porting the changes across to your tree now.
> > 
> > Cheers,
> > Rusty.
> 
> Hi Ingo,
> 
> It would seem easier to back out previous patches and apply the 
> replacements. Does this work for you?

no, it does not work fine. As i said, i reworked various small bits 
along the way of reviewing and integrating them, under the obvious 
assumption that you submitted the latest and greatest. I spent hours 
testing every single step as well. If you cannot get your workflow right 
then we cannot have this stuff in v2.6.28.

So ... please send append-only changes against tip/cpus4096-v2. We can 
squash/backmerge any bits to keep it all clean, but all changes have to 
be fully visible and fully reviewed from now on, because time is running 
short.

	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/