From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
heiko carstens <heiko.carstens@de.ibm.com>,
Andy Lutomirski <luto@amacapital.net>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-api <linux-api@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Boqun Feng <boqun.feng@gmail.com>,
Dave Watson <davejwatson@fb.com>, Paul Turner <pjt@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Russell King <linux@arm.linux.org.uk>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Chris Lameter <cl@linux.com>, Ben Maurer <bmaurer@fb.com>,
rostedt <rostedt@goodmis.org>,
Josh Triplett <josh@joshtriplett.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will
Subject: Re: [RFC PATCH for 4.18] rseq: use __u64 for rseq_cs fields, validate user inputs
Date: Tue, 3 Jul 2018 14:41:01 -0400 (EDT) [thread overview]
Message-ID: <1368400582.11897.1530643261772.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20180703182837.GC2494@hirez.programming.kicks-ass.net>
----- On Jul 3, 2018, at 2:28 PM, Peter Zijlstra peterz@infradead.org wrote:
> On Tue, Jul 03, 2018 at 02:15:34PM -0400, Mathieu Desnoyers wrote:
>> ----- On Jul 3, 2018, at 2:11 PM, Peter Zijlstra peterz@infradead.org wrote:
>>
>> > On Tue, Jul 03, 2018 at 01:58:37PM -0400, Mathieu Desnoyers wrote:
>> >> I can modify the ABI to put the cpu_id_start and cpu_id fields inside
>> >> a union, and update it with a single store.
>> >>
>> >> Thoughts ?
>> >
>> > Let's keep them for now, we can always frob this later, they are aligned
>> > and proper, no need to expose that union to userspace.
>>
>> Isn't it weird to change the API of an exposed public uapi header ?
>
> Sure, just keep it as is. We don't need an exposed union to do a single
> store there.
>
> Something like the ugly below preserves API but still does a single
> store.
>
> But sure, if you want to expose that union for some reason, then now is
> the time.
User-space won't ever want to read cpu_id_start and cpu_id from a single
u64 load, it serves no purpose to do so. So I'm OK with keeping those as
is and defining a local union for the __put_user() update.
Thanks!
Mathieu
>
> diff --git a/kernel/rseq.c b/kernel/rseq.c
> index 22b6acf1ad63..e956c48b5f83 100644
> --- a/kernel/rseq.c
> +++ b/kernel/rseq.c
> @@ -85,10 +85,17 @@ static int rseq_update_cpu_id(struct task_struct *t)
> {
> u32 cpu_id = raw_smp_processor_id();
>
> - if (__put_user(cpu_id, &t->rseq->cpu_id_start))
> - return -EFAULT;
> - if (__put_user(cpu_id, &t->rseq->cpu_id))
> + union {
> + struct {
> + u32 cpu_id_start;
> + u32 cpu_id;
> + };
> + u64 val;
> + } x = { { .cpu_id_start = cpu_id, .cpu_id = cpu_id, } };
> +
> + if (__put_user(x.val, (u64 *)&t->rseq->cpu_id_start))
> return -EFAULT;
> +
> trace_rseq_update(t);
> return 0;
> }
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2018-07-03 18:41 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 22:31 [RFC PATCH for 4.18] rseq: use __u64 for rseq_cs fields, validate user inputs Mathieu Desnoyers
2018-07-02 22:45 ` Linus Torvalds
2018-07-02 23:00 ` Mathieu Desnoyers
2018-07-02 23:06 ` Linus Torvalds
2018-07-02 23:16 ` Mathieu Desnoyers
2018-07-02 23:22 ` Linus Torvalds
2018-07-02 23:25 ` Mathieu Desnoyers
2018-07-02 23:22 ` Mathieu Desnoyers
2018-07-02 23:37 ` Andy Lutomirski
2018-07-03 1:19 ` Mathieu Desnoyers
2018-07-03 2:01 ` Mathieu Desnoyers
2018-07-03 2:18 ` Linus Torvalds
2018-07-03 2:30 ` Mathieu Desnoyers
2018-07-03 2:33 ` Andy Lutomirski
2018-07-03 2:44 ` Linus Torvalds
2018-07-03 8:14 ` Peter Zijlstra
2018-07-03 8:29 ` Heiko Carstens
2018-07-03 8:43 ` Peter Zijlstra
2018-07-03 8:55 ` Heiko Carstens
2018-07-03 9:17 ` Heiko Carstens
2018-07-03 9:24 ` Peter Zijlstra
2018-07-03 9:21 ` Peter Zijlstra
2018-07-03 16:40 ` Andi Kleen
2018-07-03 17:02 ` Peter Zijlstra
2018-07-03 17:06 ` Andy Lutomirski
2018-07-03 17:10 ` Linus Torvalds
2018-07-03 17:26 ` Mathieu Desnoyers
2018-07-03 17:34 ` Peter Zijlstra
2018-07-03 17:38 ` Mathieu Desnoyers
2018-07-03 17:48 ` Peter Zijlstra
2018-07-03 17:58 ` Mathieu Desnoyers
2018-07-03 18:11 ` Peter Zijlstra
2018-07-03 18:15 ` Mathieu Desnoyers
2018-07-03 18:28 ` Peter Zijlstra
2018-07-03 18:41 ` Mathieu Desnoyers [this message]
2018-07-03 19:08 ` Peter Zijlstra
2018-07-03 17:59 ` Linus Torvalds
2018-07-03 18:09 ` Mathieu Desnoyers
2018-07-03 18:10 ` Peter Zijlstra
2018-07-03 0:19 ` Christopher Lameter
2018-07-03 0:23 ` Mathieu Desnoyers
2018-07-03 0:35 ` Christopher Lameter
2018-07-03 1:17 ` Mathieu Desnoyers
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=1368400582.11897.1530643261772.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=bmaurer@fb.com \
--cc=boqun.feng@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=davejwatson@fb.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=josh@joshtriplett.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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).