[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140520172134.GJ2185@moon>
Date: Tue, 20 May 2014 21:21:34 +0400
From: Cyrill Gorcunov <gorcunov@...il.com>
To: Andy Lutomirski <luto@...capital.net>
Cc: x86@...nel.org, Andrew Morton <akpm@...ux-foundation.org>,
Sasha Levin <sasha.levin@...cle.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Dave Jones <davej@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
Pavel Emelyanov <xemul@...allels.com>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH 3/4] x86,mm: Improve _install_special_mapping and fix x86
vdso naming
On Mon, May 19, 2014 at 03:58:33PM -0700, Andy Lutomirski wrote:
> Using arch_vma_name to give special mappings a name is awkward. x86
> currently implements it by comparing the start address of the vma to
> the expected address of the vdso. This requires tracking the start
> address of special mappings and is probably buggy if a special vma
> is split or moved.
>
> Improve _install_special_mapping to just name the vma directly. Use
> it to give the x86 vvar area a name, which should make CRIU's life
> easier.
>
> As a side effect, the vvar area will show up in core dumps. This
> could be considered weird and is fixable. Thoughts?
>
> Cc: Cyrill Gorcunov <gorcunov@...nvz.org>
> Cc: Pavel Emelyanov <xemul@...allels.com>
> Signed-off-by: Andy Lutomirski <luto@...capital.net>
Hi Andy, thanks a lot for this! I must confess I don't yet know how
would we deal with compat tasks but this is 'must have' mark which
allow us to detect vvar area!
--
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/
Powered by blists - more mailing lists