From: "H. Peter Anvin" <hpa@zytor.com>
To: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, x86l <x86@kernel.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Andy Lutomirski <luto@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: yaomin2@huawei.com
Subject: Re: Is this a kernel BUG? ///Re: [Question] Can we use SIGRTMIN when vdso disabled on X86?
Date: Thu, 7 Jun 2018 14:05:45 -0700 [thread overview]
Message-ID: <64b61360-803d-b987-6721-e9eb0ebe63a7@zytor.com> (raw)
In-Reply-To: <5B188E2B.7040700@huawei.com>
On 06/06/18 18:45, Leizhen (ThunderTown) wrote:
>>
>> The use of signals without SA_RESTORER is considered obsolete, but it's somewhat surprising that the vdso isn't there; it should be mapped even for static binaries esp. on i386 since it is the preferred way to do system calls (you don't need to parse the ELF for that.) Are you explicitly disabling the VDSO? If so, Don't Do That.
>
> Yes, the vdso was explicitly disabled by the tester. Thanks.
>
Are there any use cases that calls for this? Maybe we should drop this
option.
-hpa
prev parent reply other threads:[~2018-06-07 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 11:24 [Question] Can we use SIGRTMIN when vdso disabled on X86? Leizhen (ThunderTown)
2018-06-06 7:52 ` Is this a kernel BUG? ///Re: " Leizhen (ThunderTown)
2018-06-06 9:17 ` Leizhen (ThunderTown)
2018-06-06 17:01 ` Andy Lutomirski
2018-06-07 2:05 ` Leizhen (ThunderTown)
2018-06-07 2:39 ` Andy Lutomirski
2018-06-07 3:10 ` Leizhen (ThunderTown)
2018-06-06 17:48 ` hpa
2018-06-07 1:45 ` Leizhen (ThunderTown)
2018-06-07 21:05 ` H. Peter Anvin [this message]
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=64b61360-803d-b987-6721-e9eb0ebe63a7@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thunder.leizhen@huawei.com \
--cc=x86@kernel.org \
--cc=yaomin2@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).