From: Dave Hansen <dave.hansen@linux.intel.com>
To: Yu-cheng Yu <yu-cheng.yu@intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@suse.de>,
Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>,
"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH 08/10] x86/xsaves: Fix PTRACE frames for XSAVES
Date: Mon, 22 Feb 2016 12:00:02 -0800 [thread overview]
Message-ID: <56CB68C2.6010003@linux.intel.com> (raw)
In-Reply-To: <1456167621-3974-1-git-send-email-yu-cheng.yu@intel.com>
On 02/22/2016 11:00 AM, Yu-cheng Yu wrote:
> + if (xsave->header.xfeatures & XFEATURE_MASK_SUPERVISOR)
> + xsave->header.xfeatures = xfeatures | XFEATURE_MASK_SUPERVISOR;
> + else
> + xsave->header.xfeatures = xfeatures;
This is dangerous. It says, "if any supervisor feature bit is set, then
set *ALL* of the known bits". There's no way that can work.
Don't you just want to or in the new bits that were in the passed-in
'xfeatures':
xsave->header.xfeatures |= xfeatures;
'xfeatures' is known not to contain any supervisor bits.
next prev parent reply other threads:[~2016-02-22 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 19:00 [PATCH 08/10] x86/xsaves: Fix PTRACE frames for XSAVES Yu-cheng Yu
2016-02-22 20:00 ` Dave Hansen [this message]
2016-02-22 20:48 ` Yu-cheng Yu
2016-02-22 22:19 ` Dave Hansen
2016-02-22 22:29 ` Yu-cheng Yu
2016-02-22 22:45 ` Andy Lutomirski
2016-02-22 22:50 ` Yu-cheng Yu
2016-02-22 22:53 ` Dave Hansen
2016-02-22 22:55 ` 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=56CB68C2.6010003@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=bp@suse.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=ravi.v.shankar@intel.com \
--cc=sai.praneeth.prakhya@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.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 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.