linux-kernel - Re: [-next Sept 9] S309 Build break (mm/percpu.c)

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: <4C89CB9D.6010005@in.ibm.com>
Date:	Fri, 10 Sep 2010 11:39:33 +0530
From:	Sachin Sant <sachinp@...ibm.com>
To:	Tejun Heo <tj@...nel.org>
CC:	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	linux-s390@...r.kernel.org,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [-next Sept 9] S309 Build break (mm/percpu.c)

Tejun Heo wrote:
> Commit bbddff05 (percpu: use percpu allocator on UP too) incorrectly
> excluded pcpu_build_alloc_info() on SMP configurations which use
> generic setup_per_cpu_area() like s390.  The config ifdefs are
> becoming confusing.  Fix and clean it up by,
>
> * Move pcpu_build_alloc_info() right on top of its two users -
>   pcpu_{embed|page}_first_chunk() which are already in CONFIG_SMP
>   block.
>
> * Define BUILD_{EMBED|PAGE}_FIRST_CHUNK which indicate whether each
>   first chunk function needs to be included and use them to control
>   inclusion of the three functions to reduce confusion.
>
> Signed-off-by: Tejun Heo <tj@...nel.org>
> Reported-by: Sachin Sant <sachinp@...ibm.com>
> ---
> Can you please test this patch?
>   
Tested the patch against yesterday's next release(20100909). Works fine.

Thanks Tejun.

Regards
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

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