[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180629134257.ci5ninozkh2ni6wd@mwanda>
Date: Fri, 29 Jun 2018 16:42:57 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Luc Van Oostenryck <luc.vanoostenryck@...il.com>
Cc: Dave Martin <Dave.Martin@....com>,
Andrey Konovalov <andreyknvl@...gle.com>,
Mark Rutland <mark.rutland@....com>,
Kate Stewart <kstewart@...uxfoundation.org>,
linux-doc@...r.kernel.org,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Paul Lawrence <paullawrence@...gle.com>,
Linux Memory Management List <linux-mm@...ck.org>,
Alexander Potapenko <glider@...gle.com>,
Chintan Pandya <cpandya@...eaurora.org>,
Christoph Lameter <cl@...ux.com>,
Ingo Molnar <mingo@...nel.org>,
Jacob Bramley <Jacob.Bramley@....com>,
Jann Horn <jannh@...gle.com>,
Mark Brand <markbrand@...gle.com>,
kasan-dev <kasan-dev@...glegroups.com>,
linux-sparse@...r.kernel.org,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Evgeniy Stepanov <eugenis@...gle.com>,
Arnd Bergmann <arnd@...db.de>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Marc Zyngier <marc.zyngier@....com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@....com>,
Ruben Ayrapetyan <Ruben.Ayrapetyan@....com>,
Mike Rapoport <rppt@...ux.vnet.ibm.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Kostya Serebryany <kcc@...gle.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
"Eric W . Biederman" <ebiederm@...ssion.com>,
Lee Smith <Lee.Smith@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>,
smatch@...r.kernel.org
Subject: Re: [PATCH v4 00/17] khwasan: kernel hardware assisted address
sanitizer
On Fri, Jun 29, 2018 at 01:26:14PM +0200, Luc Van Oostenryck wrote:
> On Fri, Jun 29, 2018 at 12:04:22PM +0100, Dave Martin wrote:
> >
> > Can sparse be hacked to identify pointer subtractions where the pointers
> > are cannot be statically proved to point into the same allocation?
>
> sparse only see the (deatils of) the function it analyses and all
> visible declarations, nothing more.
>
> It would be more a job for smatch which do global analysis.
> But to identify such subtractions yu must already have a (good)
> pointer alias analysis which I don't think smatch do (but I can
> be wrong, Dan & smatch's ml added in CC).
That would be hard to manage. Maybe in a year from now...
Pointer math errors tend to get caught pretty quick because they're on
the success path so I don't imagine there are huge numbers of bugs.
regards,
dan carpenter
Powered by blists - more mailing lists