Re: [RFC][PATCH] x86: Verify access_ok() context
From: Frank Ch. Eigler
Date: Thu Jan 19 2017 - 15:22:23 EST
Hi, Thomas -
On Thu, Jan 19, 2017 at 07:12:48PM +0100, Thomas Gleixner wrote:
> [...]
> It does matter very much, because the fact that the warning triggers tells
> me that it's placed in code which is NOT executed in task context.
> [...]
> We are not papering over problems.
Understood. We were interpreting the comments around access_ok to
mean that the underlying hazard condition was different (stricter)
than in_task(). If the warning could be made to match that hazard
condition more precisely, then safe but non-in_task() callers can use
access_ok() without the warning.
- FChE