From: Peter Zijlstra <peterz@infradead.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
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 Deacon <will.deacon@arm.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Joel Fernandes <joelaf@google.com>,
Michal Simek <michal.simek@xilinx.com>,
schwidefsky <schwidefsky@de.ibm.com>, gor <gor@linux.ibm.com>
Subject: Re: [RFC PATCH for 4.18] rseq: use __u64 for rseq_cs fields, validate user inputs
Date: Tue, 3 Jul 2018 21:08:31 +0200 [thread overview]
Message-ID: <20180703190831.GJ2458@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1368400582.11897.1530643261772.JavaMail.zimbra@efficios.com>
On Tue, Jul 03, 2018 at 02:41:01PM -0400, Mathieu Desnoyers wrote:
> 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.
So I think previously we had the sequence number and cpuid in there
together, and in that case it did want to load them both. But since you
made that sequence number dissapear....
next prev parent reply other threads:[~2018-07-03 19:09 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 22:31 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
2018-07-03 19:08 ` Peter Zijlstra [this message]
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=20180703190831.GJ2458@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=joelaf@google.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=mathieu.desnoyers@efficios.com \
--cc=michal.simek@xilinx.com \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.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
Powered by JetHome