All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Dmitry Safonov <dsafonov@virtuozzo.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
	luto@amacapital.net, tglx@linutronix.de, hpa@zytor.com,
	x86@kernel.org, akpm@linux-foundation.org, linux-mm@kvack.org,
	0x7f454c46@gmail.com, Shuah Khan <shuahkh@osg.samsung.com>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCHv8 resend 2/2] selftest/x86: add mremap vdso test
Date: Mon, 16 May 2016 15:54:42 +0200	[thread overview]
Message-ID: <20160516135442.GA14452@gmail.com> (raw)
In-Reply-To: <1462886951-23376-2-git-send-email-dsafonov@virtuozzo.com>


* Dmitry Safonov <dsafonov@virtuozzo.com> wrote:

> Should print on success:
> [root@localhost ~]# ./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@localhost ~]# ./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?

Thanks,

	Ingo

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Dmitry Safonov <dsafonov@virtuozzo.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
	luto@amacapital.net, tglx@linutronix.de, hpa@zytor.com,
	x86@kernel.org, akpm@linux-foundation.org, linux-mm@kvack.org,
	0x7f454c46@gmail.com, Shuah Khan <shuahkh@osg.samsung.com>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCHv8 resend 2/2] selftest/x86: add mremap vdso test
Date: Mon, 16 May 2016 15:54:42 +0200	[thread overview]
Message-ID: <20160516135442.GA14452@gmail.com> (raw)
In-Reply-To: <1462886951-23376-2-git-send-email-dsafonov@virtuozzo.com>


* Dmitry Safonov <dsafonov@virtuozzo.com> wrote:

> Should print on success:
> [root@localhost ~]# ./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@localhost ~]# ./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?

Thanks,

	Ingo

  reply	other threads:[~2016-05-16 13:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 13:29 [PATCHv8 resend 1/2] x86/vdso: add mremap hook to vm_special_mapping Dmitry Safonov
2016-05-10 13:29 ` Dmitry Safonov
2016-05-10 13:29 ` [PATCHv8 resend 2/2] selftest/x86: add mremap vdso test Dmitry Safonov
2016-05-10 13:29   ` Dmitry Safonov
2016-05-16 13:54   ` Ingo Molnar [this message]
2016-05-16 13:54     ` Ingo Molnar
2016-05-16 16:24     ` Dmitry Safonov
2016-05-16 16:24       ` Dmitry Safonov
2016-05-16 18:25       ` Andy Lutomirski
2016-05-16 18:25         ` Andy Lutomirski
2016-05-17 10:25         ` Dmitry Safonov
2016-05-17 10:25           ` Dmitry Safonov
2016-05-16  9:38 ` [PATCHv8 resend 1/2] x86/vdso: add mremap hook to vm_special_mapping Dmitry Safonov
2016-05-16  9:38   ` Dmitry Safonov
2016-05-16 10:54   ` Ingo Molnar
2016-05-16 10:54     ` Ingo Molnar
2016-05-16 11:14     ` Dmitry Safonov
2016-05-16 11:14       ` Dmitry Safonov
2016-05-16 13:55       ` Ingo Molnar
2016-05-16 13:55         ` Ingo Molnar
2016-05-16 16:23         ` Dmitry Safonov
2016-05-16 16:23           ` Dmitry Safonov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160516135442.GA14452@gmail.com \
    --to=mingo@kernel.org \
    --cc=0x7f454c46@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dsafonov@virtuozzo.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=shuahkh@osg.samsung.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.