linux-kernel - Re: [stable] [PATCH -stable] vmalloc: conditionalize build of pcpu_get_vm

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:	Wed, 16 Dec 2009 15:12:10 -0800
From:	Greg KH <greg@...ah.com>
To:	Tejun Heo <teheo@...ell.com>
Cc:	stable@...nel.org, tony.luck@...el.com, linux-ia64@...r.kernel.org,
	linux-kernel@...r.kernel.org, Jan Beulich <JBeulich@...ell.com>,
	linux-mm@...ck.org, Geert Uytterhoeven <geert@...ux-m68k.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [stable] [PATCH -stable] vmalloc: conditionalize build of
 pcpu_get_vm_areas()

On Thu, Dec 10, 2009 at 08:43:16AM +0900, Tejun Heo wrote:
> pcpu_get_vm_areas() is used only when dynamic percpu allocator is used
> by the architecture.  In 2.6.32, ia64 doesn't use dynamic percpu
> allocator and has a macro which makes pcpu_get_vm_areas() buggy via
> local/global variable aliasing and triggers compile warning.
> 
> The problem is fixed in upstream and ia64 uses dynamic percpu
> allocators, so the only left issue is inclusion of unnecessary code
> and compile warning on ia64 on 2.6.32.
> 
> Don't build pcpu_get_vm_areas() if legacy percpu allocator is in use.
> 
> Signed-off-by: Tejun Heo <tj@...nel.org>
> Reported-by: Jan Beulich <JBeulich@...ell.com>
> Cc: stable@...nel.org
> ---
> Please note that this commit won't appear on upstream.

So this is only needed for the .32 kernel stable tree?  Not .31?  And
it's not upstream as it was solved differently there?

thanks,

greg k-h
--
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/