[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190227143313.GK32534@hirez.programming.kicks-ass.net>
Date: Wed, 27 Feb 2019 15:33:13 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Andrey Ryabinin <aryabinin@...tuozzo.com>
Cc: torvalds@...ux-foundation.org, tglx@...utronix.de, hpa@...or.com,
julien.thierry@....com, will.deacon@....com, luto@...capital.net,
mingo@...nel.org, catalin.marinas@....com, james.morse@....com,
valentin.schneider@....com, brgerst@...il.com, jpoimboe@...hat.com,
luto@...nel.org, bp@...en8.de, dvlasenk@...hat.com,
linux-kernel@...r.kernel.org, glider@...gle.com, dvyukov@...gle.com
Subject: Re: [PATCH 5/6] objtool: Add UACCESS validation
On Wed, Feb 27, 2019 at 03:26:23PM +0100, Peter Zijlstra wrote:
> On Wed, Feb 27, 2019 at 05:17:58PM +0300, Andrey Ryabinin wrote:
> >
> >
> > On 2/27/19 5:08 PM, Peter Zijlstra wrote:
>
> > > I can't actually find any definitions of those functions, so I can't
> > > very well mark the safe, even if we wanted to.
> > >
> >
> > They are macro-generated. Use 'git grep DEFINE_ASAN'
>
> Ah, indeed! I'll go have a look.
Urgh, kasan_report() is definitely unsafe. Now, admitedly we should
'never' hit that, but it does leave us up a creek without a paddle.
Not sure what to do here; best I can come up with atm. is kill SMAP on
KASAN builds.
Powered by blists - more mailing lists