[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1701162211570.3923@nanos>
Date: Mon, 16 Jan 2017 22:14:31 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: David Smith <dsmith@...hat.com>
cc: Peter Zijlstra <peterz@...radead.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>,
Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Frank Ch. Eigler" <fche@...hat.com>
Subject: Re: [RFC][PATCH] x86: Verify access_ok() context
On Mon, 16 Jan 2017, David Smith wrote:
> If you call access_ok() with page faulting disabled, you'll still see
> this new warning.
And how so? It's just checking for task context. page fault disable/enable
has absolutely nothing to do with that.
> If you put that new access_ok() call in a module that gets
> loaded/unloaded, you see one warning for every module load, which gets a
> bit annoying.
Can you please elaborate where this access_ok() is placed in the module
code?
Thanks,
tglx
Powered by blists - more mailing lists