From: "H. Peter Anvin" <hpa@zytor.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andy Lutomirski <luto@amacapital.net>,
Anish Bhatt <anish@chelsio.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Sebastian Lackner <sebastian@fds-team.de>
Subject: Re: [PATCH] x86 : Ensure X86_FLAGS_NT is cleared on syscall entry
Date: Mon, 29 Sep 2014 13:01:43 -0700 [thread overview]
Message-ID: <5429BAA7.8060406@zytor.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1409292152270.22082@ionos.tec.linutronix.de>
On 09/29/2014 12:57 PM, Thomas Gleixner wrote:
>
>> I think we should mask the bit anyway.
>
> I tend to disagree. If we clear it there we need to consequentely
> audit ALL other possibilites and if there are any we need to clear the
> bit there as well. Just to make buggy user space happy?
>
The entry options into the kernel are: interrupt/exception (already
known to be OK), SYSENTER32, SYSCALL32, and SYSCALL64. It is not too
much to work through those issues, I don't think.
-hpa
next prev parent reply other threads:[~2014-09-29 20:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 19:42 [PATCH] x86 : Ensure X86_FLAGS_NT is cleared on syscall entry Anish Bhatt
2014-09-25 23:00 ` Chuck Ebbert
2014-09-29 17:30 ` Andy Lutomirski
2014-09-26 22:00 ` Chuck Ebbert
2014-09-26 22:10 ` Anish Bhatt
2014-09-26 23:32 ` Linus Torvalds
2014-09-29 17:40 ` Andy Lutomirski
2014-09-29 18:30 ` Sebastian Lackner
2014-09-29 18:43 ` Andy Lutomirski
2014-09-29 19:33 ` Thomas Gleixner
2014-09-29 19:41 ` Sebastian Lackner
2014-09-29 19:51 ` Thomas Gleixner
2014-09-29 18:59 ` Thomas Gleixner
2014-09-29 19:08 ` Andy Lutomirski
2014-09-29 19:17 ` Andy Lutomirski
2014-09-29 19:41 ` Thomas Gleixner
2014-09-29 19:43 ` H. Peter Anvin
2014-09-29 19:57 ` Thomas Gleixner
2014-09-29 20:01 ` H. Peter Anvin [this message]
2014-09-29 20:10 ` Thomas Gleixner
2014-09-29 20:29 ` Andy Lutomirski
2014-09-29 20:16 ` Andy Lutomirski
2014-09-29 21:37 ` Thomas Gleixner
2014-09-30 0:11 ` Andy Lutomirski
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=5429BAA7.8060406@zytor.com \
--to=hpa@zytor.com \
--cc=anish@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=sebastian@fds-team.de \
--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.