linux-kernel - Re: [PATCH 00/12] cpumask: reduce stack pressure from local/passed cpumask variables v2

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: <20080326061824.GB18301@elte.hu>
Date:	Wed, 26 Mar 2008 07:18:24 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Mike Travis <travis@....com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/12] cpumask: reduce stack pressure from local/passed
	cpumask variables v2

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

> Modify usage of cpumask_t variables to use pointers as much as 
> possible.

hm, why is there no minimal patch against -git that does nothing but 
introduces the new pointer based generic APIs (without using them) - 
such as set_cpus_allowed_ptr(), etc.? Once that is upstream all the 
remaining changes can trickle one arch and one subsystem at a time, and 
once that's done, the old set_cpus_allowed() can be removed. This is far 
more manageable than one large patch.

and the cpumask_of_cpu() change should be Kconfig based initially - once 
all arches have moved to it (or even sooner) we can remove that.

	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/