linux-kernel - Re: [PATCH -tip/cpus4096-v2] cpumask: fix cpumask of call_function

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: <200810280921.14821.rusty@rustcorp.com.au>
Date:	Tue, 28 Oct 2008 09:21:14 +1100
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>,
	Mike Travis <travis@....com>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH -tip/cpus4096-v2] cpumask: fix cpumask of call_function_data

On Monday 27 October 2008 23:55:12 Ingo Molnar wrote:
> * Rusty Russell <rusty@...tcorp.com.au> wrote:
> > On Friday 24 October 2008 15:47:20 Hiroshi Shimamoto wrote:
> > > From: Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>
> >
> > Ingo, because of these concerns I recommend you revert
> > d4de5ac3b5e70928c86e3e5ac311f16cbf2e9ab3 (cpumask:
> > smp_call_function_many()) for now, and apply this less contentious
> > version.
>
> ok - applied it to tip/cpus4096-v2, thanks Rusty!
>
> If there's any chance for this in v2.6.28 then only if we disable the
> dynamic API branch altogether [CONFIG_MAXCPUS] and keep that for
> v2.6.29. This means we'd bring in the API changes which should have
> trivial impact only - and none of the riskier changes.

Agreed.  The important thing is to get the new APIs in place so we can feed 
the updates to various maintainers (esp. arch maintainers).

Thanks,
Rusty.
--
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/