* Dmitry Vyukov wrote:
> > Hm, exactly how is the 'red zone' defined? Is this about the current task
> > mostly, or when doing get_wchan() on other tasks?
>
> When code is compiled with AddressSanitizer, most variables on stack have
> redzones around them, on entry function "poisons" these
On 10/13/2015 04:57 PM, Dmitry Vyukov wrote:
> On Tue, Oct 13, 2015 at 3:48 PM, Ingo Molnar wrote:
>>
>> * Andrey Ryabinin wrote:
>>
>>> get_wchan() is racy by design, it may access volatile stack
>>> of running task, thus it may access redzone in a stack frame
>>> and cause KASAN to warn
On 10/13/2015 04:48 PM, Ingo Molnar wrote:
>
> * Andrey Ryabinin wrote:
>
>> get_wchan() is racy by design, it may access volatile stack
>> of running task, thus it may access redzone in a stack frame
>> and cause KASAN to warn about this.
>>
>> Use READ_ONCE_NOCHECK() to silence these
On Tue, Oct 13, 2015 at 3:48 PM, Ingo Molnar wrote:
>
> * Andrey Ryabinin wrote:
>
>> get_wchan() is racy by design, it may access volatile stack
>> of running task, thus it may access redzone in a stack frame
>> and cause KASAN to warn about this.
>>
>> Use READ_ONCE_NOCHECK() to silence these
* Andrey Ryabinin wrote:
> get_wchan() is racy by design, it may access volatile stack
> of running task, thus it may access redzone in a stack frame
> and cause KASAN to warn about this.
>
> Use READ_ONCE_NOCHECK() to silence these warnings.
>
> Reported-by: Sasha Levin
> Signed-off-by:
On 10/13/2015 04:48 PM, Ingo Molnar wrote:
>
> * Andrey Ryabinin wrote:
>
>> get_wchan() is racy by design, it may access volatile stack
>> of running task, thus it may access redzone in a stack frame
>> and cause KASAN to warn about this.
>>
>> Use
* Andrey Ryabinin wrote:
> get_wchan() is racy by design, it may access volatile stack
> of running task, thus it may access redzone in a stack frame
> and cause KASAN to warn about this.
>
> Use READ_ONCE_NOCHECK() to silence these warnings.
>
> Reported-by: Sasha
On Tue, Oct 13, 2015 at 3:48 PM, Ingo Molnar wrote:
>
> * Andrey Ryabinin wrote:
>
>> get_wchan() is racy by design, it may access volatile stack
>> of running task, thus it may access redzone in a stack frame
>> and cause KASAN to warn about this.
>>
* Dmitry Vyukov wrote:
> > Hm, exactly how is the 'red zone' defined? Is this about the current task
> > mostly, or when doing get_wchan() on other tasks?
>
> When code is compiled with AddressSanitizer, most variables on stack have
> redzones around them, on entry
On 10/13/2015 04:57 PM, Dmitry Vyukov wrote:
> On Tue, Oct 13, 2015 at 3:48 PM, Ingo Molnar wrote:
>>
>> * Andrey Ryabinin wrote:
>>
>>> get_wchan() is racy by design, it may access volatile stack
>>> of running task, thus it may access redzone in a
10 matches
Mail list logo