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
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
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
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
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
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
6 matches
Mail list logo