[PATCH for 4.18 2/6] rseq: use get_user/put_user rather than __get_user/__put_user
From: torvalds@linux-foundation.org (Linus Torvalds)
Date: 2018-07-09 19:05:01
Also in:
linux-api, lkml
Possibly related (same subject, not in this thread)
- 2018-07-09 · [PATCH for 4.18 2/6] rseq: use get_user/put_user rather than __get_user/__put_user · Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
On Mon, Jul 9, 2018 at 11:19 AM Mathieu Desnoyers [off-list ref] wrote:
Given that this memory area has already been checked with access_ok()
on rseq registration, are you fine with leaving
__get_user/__put_user/__copy_{from,to}_user in place so we do the
minimal change at this stage of rc, or should I go ahead and replace
the lot with get_user/put_user/copy_{from,to}_user ?
Do the full replacement, and let's get this over and done with.
Linus