On Tue, 12 Jan 2021 at 22:16, Andrey Konovalov wrote:
>
> On Tue, Jan 12, 2021 at 3:32 PM Marco Elver wrote:
> >
> > > +/*
> > > + * Unlike kasan_check_read/write(), kasan_check_byte() is performed even
> > > for
> > > + * the hardware tag-based mode that doesn't rely on compiler
> > >
On Tue, Jan 12, 2021 at 3:32 PM Marco Elver wrote:
>
> > +/*
> > + * Unlike kasan_check_read/write(), kasan_check_byte() is performed even
> > for
> > + * the hardware tag-based mode that doesn't rely on compiler
> > instrumentation.
> > + */
>
> We have too many check-functions, and the name
On Tue, Jan 05, 2021 at 07:27PM +0100, Andrey Konovalov wrote:
> The currently existing kasan_check_read/write() annotations are intended
> to be used for kernel modules that have KASAN compiler instrumentation
> disabled. Thus, they are only relevant for the software KASAN modes that
> rely on
The currently existing kasan_check_read/write() annotations are intended
to be used for kernel modules that have KASAN compiler instrumentation
disabled. Thus, they are only relevant for the software KASAN modes that
rely on compiler instrumentation.
However there's another use case for these
4 matches
Mail list logo