Messages in this thread | | | Date | Sun, 18 Oct 2015 09:24:02 +0200 | From | Ingo Molnar <> | Subject | Re: [PATCH v4 1/2] compiler, atomics: Provide READ_ONCE_NOKSAN() |
| |
* Andrey Ryabinin <aryabinin@virtuozzo.com> wrote:
> On 10/16/2015 01:33 PM, Borislav Petkov wrote: > > On Fri, Oct 16, 2015 at 12:44:53PM +0300, Andrey Ryabinin wrote: > >> Some code may perform racy by design memory reads. This could be > >> harmless, yet such code may produce KASAN warnings. > >> > >> To hide such accesses from KASAN this patch introduces > >> READ_ONCE_NOKSAN() macro. KASAN will not check the memory > >> accessed by READ_ONCE_NOKSAN(). The KernelThreadSanitizer (KTSAN) > >> is going to ignore it as well. > > > > Frankly, the "NOKSAN" suffix is too specific. I know, I know, I'm > > bikeshedding but what happens if yet another tool wants to be disabled > > from checking there and that tool is not *SAN? We rename again? > > > > So the "NOCHECK" suffix made much more sense, even if it was generic. > > IMNSVHO. > > > > Sounds reasonable. > Ingo, what do you think?
Fine with me too.
Thanks,
Ingo
| |