On 03/30/2016 02:41 AM, Michael Ellerman wrote:
> The merge window just closed, I'm still recovering.
>
> I've got it in my fixes branch locally, I'll probably push that today to
> linux-next.
Thank you.
>
> cheers
>
Sebastian
___
Linuxppc-dev mailin
On Tue, 2016-03-29 at 15:40 +0200, Sebastian Andrzej Siewior wrote:
> On 2016-03-10 01:04:24 [+0530], Aneesh Kumar K.V wrote:
> > Sebastian Andrzej Siewior writes:
>
> *ping*
> http://patchwork.ozlabs.org/patch/593943/
*pong*
The merge window just closed, I'm still recovering.
I've got it in
On 2016-03-10 01:04:24 [+0530], Aneesh Kumar K.V wrote:
> Sebastian Andrzej Siewior writes:
*ping*
http://patchwork.ozlabs.org/patch/593943/
> > [ text/plain ]
> > hugepd_free() used __get_cpu_var() once. Nothing ensured that the code
> > accessing the variable did not migrate from one CPU to an
Sebastian Andrzej Siewior writes:
> [ text/plain ]
> hugepd_free() used __get_cpu_var() once. Nothing ensured that the code
> accessing the variable did not migrate from one CPU to another and soon
> this was noticed by Tiejun Chen in 94b09d755462 ("powerpc/hugetlb:
> Replace __get_cpu_var with g
hugepd_free() used __get_cpu_var() once. Nothing ensured that the code
accessing the variable did not migrate from one CPU to another and soon
this was noticed by Tiejun Chen in 94b09d755462 ("powerpc/hugetlb:
Replace __get_cpu_var with get_cpu_var"). So we had it fixed.
Christoph Lameter was doin