linux-kernel - Re: [PATCH] percpu: Resolve ambiguities in __get_cpu_var/cpumask_var

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:	Tue, 9 Sep 2014 07:14:27 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Mel Gorman <mgorman@...e.de>
Cc:	Christoph Lameter <cl@...ux.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] percpu: Resolve ambiguities in
 __get_cpu_var/cpumask_var_t -fix

On Mon, Sep 08, 2014 at 11:06:54PM +0100, Mel Gorman wrote:
> A commit in linux-next was causing boot to fail and bisection identified
> the patch "percpu: Resolve ambiguities in __get_cpu_var/cpumask_var_".
> The commit ID is worthless as it's a linux-next commit. One of the changes

It is actually a stable commit ID.  I'll add the commit ID in the
change log.

> in that patch looks very suspicious. Reverting the full patch fixes boot
> as does this fixlet.

Applying to percpu/for-3.18-consistent-ops.

Thanks.

-- 
tejun
--
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/