From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Julien Grall <julien.grall@arm.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86: polish __{get,put}_user_{,no}check()
Date: Thu, 4 May 2017 18:52:08 +0100 [thread overview]
Message-ID: <f0c100aa-2664-29ab-1526-db10186132e5@citrix.com> (raw)
In-Reply-To: <3845e8e7-fefa-ea41-d8fd-8e79075f6096@arm.com>
On 04/05/17 09:52, Julien Grall wrote:
> Hi,
>
> On 02/05/17 14:23, Jan Beulich wrote:
>> The primary purpose is correcting a latent bug in __get_user_check()
>> (the macro has no active user at present): The access_ok() check should
>> be before the actual access, or else any PV guest could initiate MMIO
>> reads with side effects.
>>
>> Clean up all four macros at once:
>> - all arguments evaluated exactly once
>> - build the "check" flavor using the "nocheck" ones, instead of open
>> coding them
>> - "int" is wide enough for error codes
>> - name local variables without using underscores as prefixes
>> - avoid pointless parentheses
>> - add blanks after commas separating parameters or arguments
>> - consistently use tabs for indentation
>>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>> ---
>> This corrects the code which would have resulted in an XSA on Xen 4.2
>> and older, if those were still security supported. For that reason I at
>> least want to explore whether this is a change we want to take for 4.9.
>
> Andrew, do you have any opinion to get this patch in Xen 4.9?
It should go in.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-04 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 13:23 [PATCH] x86: polish __{get,put}_user_{,no}check() Jan Beulich
2017-05-02 14:28 ` Andrew Cooper
2017-05-02 14:40 ` Jan Beulich
2017-05-03 19:05 ` Andrew Cooper
2017-05-04 8:52 ` Julien Grall
2017-05-04 17:52 ` Andrew Cooper [this message]
2017-05-04 17:53 ` Julien Grall
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=f0c100aa-2664-29ab-1526-db10186132e5@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=xen-devel@lists.xenproject.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 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).