Re: linux-next: build problems (Was: [PATCH v3 1/2] Provide READ_ONCE_NOCHECK())

2015-10-15 Thread Andrey Ryabinin
On 10/15/2015 12:18 PM, Stephen Rothwell wrote: > Hi Andrey, > > On Tue, 13 Oct 2015 18:28:07 +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

linux-next: build problems (Was: [PATCH v3 1/2] Provide READ_ONCE_NOCHECK())

2015-10-15 Thread Stephen Rothwell
Hi Andrey, On Tue, 13 Oct 2015 18:28:07 +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_NOCHECK() > macro. KASAN will not

Re: linux-next: build problems (Was: [PATCH v3 1/2] Provide READ_ONCE_NOCHECK())

2015-10-15 Thread Andrey Ryabinin
On 10/15/2015 12:18 PM, Stephen Rothwell wrote: > Hi Andrey, > > On Tue, 13 Oct 2015 18:28:07 +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

linux-next: build problems (Was: [PATCH v3 1/2] Provide READ_ONCE_NOCHECK())

2015-10-15 Thread Stephen Rothwell
Hi Andrey, On Tue, 13 Oct 2015 18:28:07 +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

[PATCH v3 1/2] Provide READ_ONCE_NOCHECK()

2015-10-13 Thread Andrey Ryabinin
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_NOCHECK() macro. KASAN will not check the memory accessed by READ_ONCE_NOCHECK(). This patch creates

[PATCH v3 1/2] Provide READ_ONCE_NOCHECK()

2015-10-13 Thread Andrey Ryabinin
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_NOCHECK() macro. KASAN will not check the memory accessed by READ_ONCE_NOCHECK(). This patch creates