[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <512f4c9c-7edc-0d12-df96-9708df5f498d@virtuozzo.com>
Date: Mon, 16 May 2016 19:24:49 +0300
From: Dmitry Safonov <dsafonov@...tuozzo.com>
To: Ingo Molnar <mingo@...nel.org>
CC: <linux-kernel@...r.kernel.org>, <mingo@...hat.com>,
<luto@...capital.net>, <tglx@...utronix.de>, <hpa@...or.com>,
<x86@...nel.org>, <akpm@...ux-foundation.org>,
<linux-mm@...ck.org>, <0x7f454c46@...il.com>,
Shuah Khan <shuahkh@....samsung.com>,
<linux-kselftest@...r.kernel.org>
Subject: Re: [PATCHv8 resend 2/2] selftest/x86: add mremap vdso test
On 05/16/2016 04:54 PM, Ingo Molnar wrote:
>
> * Dmitry Safonov <dsafonov@...tuozzo.com> wrote:
>
>> Should print on success:
>> [root@...alhost ~]# ./test_mremap_vdso_32
>> AT_SYSINFO_EHDR is 0xf773f000
>> [NOTE] Moving vDSO: [f773f000, f7740000] -> [a000000, a001000]
>> [OK]
>> Or segfault if landing was bad (before patches):
>> [root@...alhost ~]# ./test_mremap_vdso_32
>> AT_SYSINFO_EHDR is 0xf774f000
>> [NOTE] Moving vDSO: [f774f000, f7750000] -> [a000000, a001000]
>> Segmentation fault (core dumped)
>
> Can the segfault be caught and recovered from, to print a proper failure message?
Will add segfault handler, thanks.
Powered by blists - more mailing lists