linux-kernel - Re: [PATCH 1/1] x86: Change _node_to_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] [day] [month] [year] [list]

Message-ID: <20080713171231.GA2988@elte.hu>
Date:	Sun, 13 Jul 2008 19:12:31 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Vegard Nossum <vegard.nossum@...il.com>
Cc:	Mike Travis <travis@....com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	mm-commits@...r.kernel.org, Yinghai Lu <yhlu.kernel@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] x86: Change _node_to_cpumask_ptr to return const
	ptr


* Vegard Nossum <vegard.nossum@...il.com> wrote:

> On Tue, Jul 8, 2008 at 11:35 PM, Mike Travis <travis@....com> wrote:
> > Subject: [PATCH 1/1] x86: Change _node_to_cpumask_ptr to return const ptr
> >
> >  * Strengthen the return type for the _node_to_cpumask_ptr to be
> >    a const pointer.  This adds compiler checking to insure that
> >    node_to_cpumask_map[] is not changed inadvertently.
> >
> > Applies to tip/master with the following patch applied:
> >
> >        "[PATCH 1/1] x86: Add check for node passed to node_to_cpumask V3"
> >
> > Signed-off-by: Mike Travis <travis@....com>
> > ---
> 
> I can successfully cross-compile the asm-generic changes with a NUMA=y 
> config on ia64 without error or warning. So I guess, at long last, you 
> may put, FWIW:
> 
>     Acked-by: Vegard Nossum <vegard.nossum@...il.com>

thanks - applied to tip/x86/core.

	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/