[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161880478605.1398509.2763333717274966533.b4-ty@ellerman.id.au>
Date: Mon, 19 Apr 2021 13:59:46 +1000
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: Dmitry Safonov <dima@...sta.com>, linux-kernel@...r.kernel.org
Cc: Paul Mackerras <paulus@...ba.org>,
Dmitry Safonov <0x7f454c46@...il.com>,
linuxppc-dev@...ts.ozlabs.org,
Laurent Dufour <ldufour@...ux.ibm.com>, stable@...r.kernel.org,
Andy Lutomirski <luto@...nel.org>,
Andrei Vagin <avagin@...il.com>
Subject: Re: [PATCH] powerpc/vdso: Separate vvar vma from vdso
On Fri, 26 Mar 2021 19:17:20 +0000, Dmitry Safonov wrote:
> Since commit 511157ab641e ("powerpc/vdso: Move vdso datapage up front")
> VVAR page is in front of the VDSO area. In result it breaks CRIU
> (Checkpoint Restore In Userspace) [1], where CRIU expects that "[vdso]"
> from /proc/../maps points at ELF/vdso image, rather than at VVAR data page.
> Laurent made a patch to keep CRIU working (by reading aux vector).
> But I think it still makes sence to separate two mappings into different
> VMAs. It will also make ppc64 less "special" for userspace and as
> a side-bonus will make VVAR page un-writable by debugger (which previously
> would COW page and can be unexpected).
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/vdso: Separate vvar vma from vdso
https://git.kernel.org/powerpc/c/1c4bce6753857dc409a0197342d18764e7f4b741
cheers
Powered by blists - more mailing lists