Re: INFO: rcu detected stall in corrupted (4)

2021-03-05 Thread Vinicius Costa Gomes
Dmitry Vyukov writes: > On Fri, Sep 4, 2020 at 8:49 PM syzbot > wrote: >> >> Hello, >> >> syzbot found the following issue on: >> >> HEAD commit:0f091e43 netlabel: remove unused param from audit_log_form.. >> git tree: net-next >> console output:

Re: INFO: rcu detected stall in corrupted (4)

2021-03-04 Thread Dmitry Vyukov
On Fri, Sep 4, 2020 at 8:49 PM syzbot wrote: > > Hello, > > syzbot found the following issue on: > > HEAD commit:0f091e43 netlabel: remove unused param from audit_log_form.. > git tree: net-next > console output: https://syzkaller.appspot.com/x/log.txt?x=14551a7190 > kernel config:

INFO: rcu detected stall in corrupted (4)

2020-09-04 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:0f091e43 netlabel: remove unused param from audit_log_form.. git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=14551a7190 kernel config: https://syzkaller.appspot.com/x/.config?x=61025c6fd3261bb1

Re: INFO: rcu detected stall in corrupted (3)

2019-04-01 Thread Juri Lelli
Hi, On 30/03/19 12:09, Borislav Petkov wrote: > On Sat, Mar 30, 2019 at 07:57:50PM +0900, Tetsuo Handa wrote: > > Yes. But what such threshold be? 0.1 second? 1 second? 10 seconds? > > Can we find a threshold where everyone can agree on? > > This is what we do all day on lkml: discussing changes

Re: INFO: rcu detected stall in corrupted (3)

2019-03-30 Thread Borislav Petkov
On Sat, Mar 30, 2019 at 11:07:40PM +0900, Tetsuo Handa wrote: > I think that syzbot should for now refrain from testing syscalls that change > scheduling related attributes, And how would we know about problems there, otherwise? -- Regards/Gruss, Boris. Good mailing practices for 400:

Re: INFO: rcu detected stall in corrupted (3)

2019-03-30 Thread Tetsuo Handa
On 2019/03/30 20:09, Borislav Petkov wrote: > On Sat, Mar 30, 2019 at 07:57:50PM +0900, Tetsuo Handa wrote: >> Yes. But what such threshold be? 0.1 second? 1 second? 10 seconds? >> Can we find a threshold where everyone can agree on? > > This is what we do all day on lkml: discussing changes so

Re: INFO: rcu detected stall in corrupted (3)

2019-03-30 Thread Borislav Petkov
On Sat, Mar 30, 2019 at 07:57:50PM +0900, Tetsuo Handa wrote: > Yes. But what such threshold be? 0.1 second? 1 second? 10 seconds? > Can we find a threshold where everyone can agree on? This is what we do all day on lkml: discussing changes so that (almost) everyone is happy with them. :-) --

Re: INFO: rcu detected stall in corrupted (3)

2019-03-30 Thread Tetsuo Handa
On 2019/03/30 19:45, Borislav Petkov wrote: > On Sat, Mar 30, 2019 at 07:40:11PM +0900, Tetsuo Handa wrote: >> But how can the scheduler be aware of various watchdogs' thresholds? > > I think what tglx means is sched_setattr() should be fixed to fail due > to the bogus value. > Yes. But what

Re: INFO: rcu detected stall in corrupted (3)

2019-03-30 Thread Borislav Petkov
On Sat, Mar 30, 2019 at 07:40:11PM +0900, Tetsuo Handa wrote: > But how can the scheduler be aware of various watchdogs' thresholds? I think what tglx means is sched_setattr() should be fixed to fail due to the bogus value. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid

Re: INFO: rcu detected stall in corrupted (3)

2019-03-30 Thread Tetsuo Handa
On 2019/03/30 16:46, Thomas Gleixner wrote: > On Sat, 30 Mar 2019, Tetsuo Handa wrote: >> This reproducer does sched_setattr(SCHED_DEADLINE) with bogus value, as with >> a reproducer for "INFO: rcu detected stall in sys_sendfile64" did. >> >> sched_setattr(0, {size=0, sched_policy=0x6 /*

Re: INFO: rcu detected stall in corrupted (3)

2019-03-30 Thread Thomas Gleixner
On Sat, 30 Mar 2019, Tetsuo Handa wrote: > On 2019/03/30 7:34, syzbot wrote: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:    8c2ffd91 Linux 5.1-rc2 > > git tree:   upstream > > console output: https://syzkaller.appspot.com/x/log.txt?x=15099d2b20 > >

Re: INFO: rcu detected stall in corrupted (3)

2019-03-29 Thread Tetsuo Handa
On 2019/03/30 7:34, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:    8c2ffd91 Linux 5.1-rc2 > git tree:   upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=15099d2b20 > kernel config: 

INFO: rcu detected stall in corrupted (3)

2019-03-29 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:8c2ffd91 Linux 5.1-rc2 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15099d2b20 kernel config: https://syzkaller.appspot.com/x/.config?x=8dcdce25ea72bedf dashboard link:

Re: INFO: rcu detected stall in corrupted

2018-05-26 Thread Dmitry Vyukov
On Thu, May 24, 2018 at 11:02 AM, Xin Long wrote: > On Thu, May 24, 2018 at 7:13 AM, Marcelo Ricardo Leitner > wrote: >> On Mon, May 21, 2018 at 11:13:46AM -0700, Eric Dumazet wrote: >>> >>> >>> On 05/21/2018 11:09 AM, David Miller wrote: >>> >

Re: INFO: rcu detected stall in corrupted

2018-05-26 Thread Dmitry Vyukov
On Thu, May 24, 2018 at 11:02 AM, Xin Long wrote: > On Thu, May 24, 2018 at 7:13 AM, Marcelo Ricardo Leitner > wrote: >> On Mon, May 21, 2018 at 11:13:46AM -0700, Eric Dumazet wrote: >>> >>> >>> On 05/21/2018 11:09 AM, David Miller wrote: >>> > From: syzbot >>> > Date: Mon, 21 May 2018 11:05:02

Re: INFO: rcu detected stall in corrupted

2018-05-24 Thread Xin Long
On Thu, May 24, 2018 at 7:13 AM, Marcelo Ricardo Leitner wrote: > On Mon, May 21, 2018 at 11:13:46AM -0700, Eric Dumazet wrote: >> >> >> On 05/21/2018 11:09 AM, David Miller wrote: >> > From: syzbot >> > Date: Mon,

Re: INFO: rcu detected stall in corrupted

2018-05-24 Thread Xin Long
On Thu, May 24, 2018 at 7:13 AM, Marcelo Ricardo Leitner wrote: > On Mon, May 21, 2018 at 11:13:46AM -0700, Eric Dumazet wrote: >> >> >> On 05/21/2018 11:09 AM, David Miller wrote: >> > From: syzbot >> > Date: Mon, 21 May 2018 11:05:02 -0700 >> > >> >> find_match+0x244/0x13a0

Re: INFO: rcu detected stall in corrupted

2018-05-23 Thread Marcelo Ricardo Leitner
On Mon, May 21, 2018 at 11:13:46AM -0700, Eric Dumazet wrote: > > > On 05/21/2018 11:09 AM, David Miller wrote: > > From: syzbot > > Date: Mon, 21 May 2018 11:05:02 -0700 > > > >> find_match+0x244/0x13a0 net/ipv6/route.c:691 > >>

Re: INFO: rcu detected stall in corrupted

2018-05-23 Thread Marcelo Ricardo Leitner
On Mon, May 21, 2018 at 11:13:46AM -0700, Eric Dumazet wrote: > > > On 05/21/2018 11:09 AM, David Miller wrote: > > From: syzbot > > Date: Mon, 21 May 2018 11:05:02 -0700 > > > >> find_match+0x244/0x13a0 net/ipv6/route.c:691 > >> find_rr_leaf net/ipv6/route.c:729 [inline] > >> rt6_select

Re: INFO: rcu detected stall in corrupted

2018-05-21 Thread David Ahern
On 5/21/18 12:13 PM, Eric Dumazet wrote: > > > On 05/21/2018 11:09 AM, David Miller wrote: >> From: syzbot >> Date: Mon, 21 May 2018 11:05:02 -0700 >> >>> find_match+0x244/0x13a0 net/ipv6/route.c:691 >>> find_rr_leaf net/ipv6/route.c:729

Re: INFO: rcu detected stall in corrupted

2018-05-21 Thread David Ahern
On 5/21/18 12:13 PM, Eric Dumazet wrote: > > > On 05/21/2018 11:09 AM, David Miller wrote: >> From: syzbot >> Date: Mon, 21 May 2018 11:05:02 -0700 >> >>> find_match+0x244/0x13a0 net/ipv6/route.c:691 >>> find_rr_leaf net/ipv6/route.c:729 [inline] >>> rt6_select net/ipv6/route.c:779 [inline]

Re: INFO: rcu detected stall in corrupted

2018-05-21 Thread Eric Dumazet
On 05/21/2018 11:09 AM, David Miller wrote: > From: syzbot > Date: Mon, 21 May 2018 11:05:02 -0700 > >> find_match+0x244/0x13a0 net/ipv6/route.c:691 >> find_rr_leaf net/ipv6/route.c:729 [inline] >> rt6_select net/ipv6/route.c:779

Re: INFO: rcu detected stall in corrupted

2018-05-21 Thread Eric Dumazet
On 05/21/2018 11:09 AM, David Miller wrote: > From: syzbot > Date: Mon, 21 May 2018 11:05:02 -0700 > >> find_match+0x244/0x13a0 net/ipv6/route.c:691 >> find_rr_leaf net/ipv6/route.c:729 [inline] >> rt6_select net/ipv6/route.c:779 [inline] > > Hmmm, endless loop in find_rr_leaf or similar?

Re: INFO: rcu detected stall in corrupted

2018-05-21 Thread David Miller
From: syzbot Date: Mon, 21 May 2018 11:05:02 -0700 > find_match+0x244/0x13a0 net/ipv6/route.c:691 > find_rr_leaf net/ipv6/route.c:729 [inline] > rt6_select net/ipv6/route.c:779 [inline] Hmmm, endless loop in find_rr_leaf or similar?

Re: INFO: rcu detected stall in corrupted

2018-05-21 Thread David Miller
From: syzbot Date: Mon, 21 May 2018 11:05:02 -0700 > find_match+0x244/0x13a0 net/ipv6/route.c:691 > find_rr_leaf net/ipv6/route.c:729 [inline] > rt6_select net/ipv6/route.c:779 [inline] Hmmm, endless loop in find_rr_leaf or similar?

INFO: rcu detected stall in corrupted

2018-05-21 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:771c577c23ba Linux 4.17-rc6 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1713435780 kernel config: https://syzkaller.appspot.com/x/.config?x=982e2df1b9e60b02 dashboard link:

INFO: rcu detected stall in corrupted

2018-05-21 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:771c577c23ba Linux 4.17-rc6 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1713435780 kernel config: https://syzkaller.appspot.com/x/.config?x=982e2df1b9e60b02 dashboard link: