linux-kernel - Re: [PULL] cpumask offstack finalization

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, 10 Feb 2011 13:44:16 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	linux-kernel@...r.kernel.org, anton@...ba.org,
	Mike Travis <travis@....com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PULL] cpumask offstack finalization


* Rusty Russell <rusty@...tcorp.com.au> wrote:

> Hi Ingo,
> 
>    A few more obsolete uses of cpumask has crept into the tree; all easily
> fixed.  This is rebased onto your -tip tree and re-tested; it finally means
> that we can detect obsolescent (and hence dangerous) cpumask usage when 
> CONFIG_CPUMASK_OFFSTACK=y.  It finally reduces the actual allocation of
> cpumask_var_t to the number of cpus we actually have.

Hm, could we get rid of the obsolete percpu APIs once and for all? The fact that 
they are still around cause the leakage into new code to begin with.

> I assume you want these via your tree: they definitely need testing across 
> architectures, though the transforms are mechanical.

Can do i guess - we can cross-test most architectures in -tip and via -next there 
will be more testing. No need to spread this out via a zillion maintainer trees i 
think.

Thanks,

	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/