On Mon, Oct 5, 2015 at 6:15 AM, Borislav Petkov <[email protected]> wrote: > On Mon, Oct 05, 2015 at 02:46:30PM +0300, Andrey Ryabinin wrote: >> It's absolutely unusable:( https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67368 >> If we add it here, it won't built because of: '__always_inline >> __read_once_size()' >> >> But, I think I have the solution. >> We could have some blacklist - list of function names which we should be >> ignored. >> In kasan_report() we could resolve return address to function name and >> compare it with name in list. >> If name in list -> ignore report. > > Sounds better. :)
These ought to be rare. probe_kernel_xyz are hopefully already covered, which leaves strange accesses to things that are known to be out of bounds, which ought to be just the memory allocation stuff (already covered?) and stack walking code (this stuff). I think that READ_ONCE_NOCHECK is a decent solution that isn't too messy. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
