On (03/01/18 16:53), Dmitry Vyukov wrote:
[..]
> > Hello Dmitry,
> >
> > I believe it's this one
> >
> > https://marc.info/?l=linux-kernel=151200883525299
>
>
> Thanks, but now that I debugged this one, I think that one is the same issue.
> Amusingly a write in READ_ONCE is actually legitimate
On (03/01/18 16:53), Dmitry Vyukov wrote:
[..]
> > Hello Dmitry,
> >
> > I believe it's this one
> >
> > https://marc.info/?l=linux-kernel=151200883525299
>
>
> Thanks, but now that I debugged this one, I think that one is the same issue.
> Amusingly a write in READ_ONCE is actually legitimate
sorry for missing the attached script in original mail, here to add it.
On Thu, 2018-03-01 at 08:47 +, Dmitry Vyukov wrote:
> On Thu, Mar 1, 2018 at 2:37 AM, Sergey Senozhatsky
> wrote:
> > Hello,
> >
> > Cc-ing Dmitry Vyukov and kasan-dev on this.
> >
> > On
sorry for missing the attached script in original mail, here to add it.
On Thu, 2018-03-01 at 08:47 +, Dmitry Vyukov wrote:
> On Thu, Mar 1, 2018 at 2:37 AM, Sergey Senozhatsky
> wrote:
> > Hello,
> >
> > Cc-ing Dmitry Vyukov and kasan-dev on this.
> >
> > On (02/28/18 16:59), Petr Mladek
On Thu, Mar 1, 2018 at 6:14 AM, Ard Biesheuvel
wrote:
> On 1 March 2018 at 14:09, Dmitry Vyukov wrote:
> ..
>> +Ard, Kees
>>
>> This is a problem with GCC_PLUGIN_STRUCTLEAK_BYREF_ALL. It inserts an
>> initializing write for __u used in READ_ONCE
On Thu, Mar 1, 2018 at 6:14 AM, Ard Biesheuvel
wrote:
> On 1 March 2018 at 14:09, Dmitry Vyukov wrote:
> ..
>> +Ard, Kees
>>
>> This is a problem with GCC_PLUGIN_STRUCTLEAK_BYREF_ALL. It inserts an
>> initializing write for __u used in READ_ONCE outside of live scope of
>> the variable.
>> Below
On Thu, Mar 1, 2018 at 4:19 PM, Sergey Senozhatsky
wrote:
> On (03/01/18 09:51), Dmitry Vyukov wrote:
>> > https://marc.info/?l=linux-kernel=151200883525299
>> >
>> > [..]
>> >> I feel lost a bit.
>> >
>> > Yeah... can't understand what's going on there.
>> >
>> >
On Thu, Mar 1, 2018 at 4:19 PM, Sergey Senozhatsky
wrote:
> On (03/01/18 09:51), Dmitry Vyukov wrote:
>> > https://marc.info/?l=linux-kernel=151200883525299
>> >
>> > [..]
>> >> I feel lost a bit.
>> >
>> > Yeah... can't understand what's going on there.
>> >
>> > The last time kasan didn't like
On (03/01/18 09:51), Dmitry Vyukov wrote:
> > https://marc.info/?l=linux-kernel=151200883525299
> >
> > [..]
> >> I feel lost a bit.
> >
> > Yeah... can't understand what's going on there.
> >
> > The last time kasan didn't like this part
> >
> > [0.00] ? console_unlock+0x605/0xcc0:
> >
On (03/01/18 09:51), Dmitry Vyukov wrote:
> > https://marc.info/?l=linux-kernel=151200883525299
> >
> > [..]
> >> I feel lost a bit.
> >
> > Yeah... can't understand what's going on there.
> >
> > The last time kasan didn't like this part
> >
> > [0.00] ? console_unlock+0x605/0xcc0:
> >
On 1 March 2018 at 14:09, Dmitry Vyukov wrote:
..
> +Ard, Kees
>
> This is a problem with GCC_PLUGIN_STRUCTLEAK_BYREF_ALL. It inserts an
> initializing write for __u used in READ_ONCE outside of live scope of
> the variable.
> Below "movb $0x1,0x0(%r13)" and "movb
On 1 March 2018 at 14:09, Dmitry Vyukov wrote:
..
> +Ard, Kees
>
> This is a problem with GCC_PLUGIN_STRUCTLEAK_BYREF_ALL. It inserts an
> initializing write for __u used in READ_ONCE outside of live scope of
> the variable.
> Below "movb $0x1,0x0(%r13)" and "movb $0xf8,0x0(%r13)" denote live
ngchul Park <byungchul.p...@lge.com>, Tejun Heo <t...@kernel.org>, Pavel
> Machek <pa...@ucw.cz>, Steven Rostedt <rost...@goodmis.org>, Sergey
> Senozhatsky <sergey.senozhat...@gmail.com>, LKML
> <linux-kernel@vger.kernel.org>, l...@01.org
> Da
ng Wang
> , Dave Hansen , Johannes
> Weiner , Mel Gorman , Michal Hocko
> , Vlastimil Babka , Peter Zijlstra
> , Linus Torvalds , Jan
> Kara , Mathieu Desnoyers ,
> Byungchul Park , Tejun Heo , Pavel
> Machek , Steven Rostedt , Sergey
> Senozhatsky , LKML
> , l...
t;sergey.senozhat...@gmail.com>, LKML <linux-kernel@vger.kernel.org>, l...@01.org
Date:Thu, 01 Mar 2018 10:08:19 +0900
Subject: Re: [lkp-robot] [printk] c162d5b433: BUG:KASAN:use-after-scope_in_c
Petr Mladek wrote:
> I am really curious what code is proceed on the li
Torvalds , Jan
Kara , Mathieu Desnoyers ,
Byungchul Park , Tejun Heo , Pavel
Machek , Steven Rostedt , Sergey Senozhatsky
, LKML , l...@01.org
Date:Thu, 01 Mar 2018 10:08:19 +0900
Subject: Re: [lkp-robot] [printk] c162d5b433: BUG:KASAN:use-after-scope_in_c
Petr Mladek wrote:
> I am r
On Thu, Mar 1, 2018 at 2:37 AM, Sergey Senozhatsky
wrote:
> Hello,
>
> Cc-ing Dmitry Vyukov and kasan-dev on this.
>
> On (02/28/18 16:59), Petr Mladek wrote:
> [..]
>> > >
>> > > [0.00] BUG: KASAN: use-after-scope in console_unlock+0x185/0x960
>> > > [
On Thu, Mar 1, 2018 at 2:37 AM, Sergey Senozhatsky
wrote:
> Hello,
>
> Cc-ing Dmitry Vyukov and kasan-dev on this.
>
> On (02/28/18 16:59), Petr Mladek wrote:
> [..]
>> > >
>> > > [0.00] BUG: KASAN: use-after-scope in console_unlock+0x185/0x960
>> > > [0.00] BUG: KASAN:
On Thu, Mar 1, 2018 at 2:37 AM, Sergey Senozhatsky
wrote:
> Hello,
>
> Cc-ing Dmitry Vyukov and kasan-dev on this.
>
> On (02/28/18 16:59), Petr Mladek wrote:
> [..]
>> > >
>> > > [0.00] BUG: KASAN: use-after-scope in console_unlock+0x185/0x960
>> > > [
On Thu, Mar 1, 2018 at 2:37 AM, Sergey Senozhatsky
wrote:
> Hello,
>
> Cc-ing Dmitry Vyukov and kasan-dev on this.
>
> On (02/28/18 16:59), Petr Mladek wrote:
> [..]
>> > >
>> > > [0.00] BUG: KASAN: use-after-scope in console_unlock+0x185/0x960
>> > > [0.00] BUG: KASAN:
Hello,
Cc-ing Dmitry Vyukov and kasan-dev on this.
On (02/28/18 16:59), Petr Mladek wrote:
[..]
> > >
> > > [0.00] BUG: KASAN: use-after-scope in console_unlock+0x185/0x960
> > > [0.00] BUG: KASAN: use-after-scope in console_unlock+0x185/0x960
> >
> > Is there any change to get
Hello,
Cc-ing Dmitry Vyukov and kasan-dev on this.
On (02/28/18 16:59), Petr Mladek wrote:
[..]
> > >
> > > [0.00] BUG: KASAN: use-after-scope in console_unlock+0x185/0x960
> > > [0.00] BUG: KASAN: use-after-scope in console_unlock+0x185/0x960
> >
> > Is there any change to get
On Wed 2018-02-28 11:23:34, Petr Mladek wrote:
> On Sat 2018-02-24 13:34:05, kernel test robot wrote:
> > TO: Petr Mladek
> > CC: Cong Wang , Dave Hansen
> > , Johannes Weiner , Mel Gorman
> >
On Wed 2018-02-28 11:23:34, Petr Mladek wrote:
> On Sat 2018-02-24 13:34:05, kernel test robot wrote:
> > TO: Petr Mladek
> > CC: Cong Wang , Dave Hansen
> > , Johannes Weiner , Mel Gorman
> > , Michal Hocko , Vlastimil Babka
> > , Peter Zijlstra , Linus Torvalds
> > , Jan Kara , Mathieu
On Sat 2018-02-24 13:34:05, kernel test robot wrote:
> TO: Petr Mladek
> CC: Cong Wang , Dave Hansen
> , Johannes Weiner , Mel Gorman
> , Michal Hocko , Vlastimil Babka
>
On Sat 2018-02-24 13:34:05, kernel test robot wrote:
> TO: Petr Mladek
> CC: Cong Wang , Dave Hansen
> , Johannes Weiner , Mel Gorman
> , Michal Hocko , Vlastimil Babka
> , Peter Zijlstra , Linus Torvalds
> , Jan Kara , Mathieu Desnoyers
> , Tetsuo Handa
> , Byungchul Park
> , Tejun Heo ,
TO: Petr Mladek
CC: Cong Wang , Dave Hansen ,
Johannes Weiner , Mel Gorman , Michal
Hocko , Vlastimil Babka , Peter Zijlstra
, Linus
TO: Petr Mladek
CC: Cong Wang , Dave Hansen ,
Johannes Weiner , Mel Gorman , Michal
Hocko , Vlastimil Babka , Peter Zijlstra
, Linus Torvalds , Jan
Kara , Mathieu Desnoyers , Tetsuo
Handa , Byungchul Park
, Tejun Heo , Pavel Machek
, Steven Rostedt (VMware) , Sergey
Senozhatsky , LKML
,
28 matches
Mail list logo