* Re: WARNING in rcu_check_gp_start_stall [not found] <0000000000007da94e05827ea99a@google.com> @ 2019-03-17 10:43 ` syzbot 2019-03-17 11:04 ` Greg KH 0 siblings, 1 reply; 3+ messages in thread From: syzbot @ 2019-03-17 10:43 UTC (permalink / raw) To: bp, devel, douly.fnst, dvyukov, forest, gregkh, hpa, konrad.wilk, len.brown, linux-kernel, linux-mm, mingo, peterz, puwen, syzkaller-bugs, tglx, tvboxspy, wang.yi59, x86 syzbot has bisected this bug to: commit f1e3e92135202ff3d95195393ee62808c109208c Author: Malcolm Priestley <tvboxspy@gmail.com> Date: Wed Jul 22 18:16:42 2015 +0000 staging: vt6655: fix tagSRxDesc -> next_desc type bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=111856cf200000 start commit: f1e3e921 staging: vt6655: fix tagSRxDesc -> next_desc type git tree: upstream final crash: https://syzkaller.appspot.com/x/report.txt?x=131856cf200000 console output: https://syzkaller.appspot.com/x/log.txt?x=151856cf200000 kernel config: https://syzkaller.appspot.com/x/.config?x=7132344728e7ec3f dashboard link: https://syzkaller.appspot.com/bug?extid=111bc509cd9740d7e4aa syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16d4966cc00000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10c492d0c00000 Reported-by: syzbot+111bc509cd9740d7e4aa@syzkaller.appspotmail.com Fixes: f1e3e921 ("staging: vt6655: fix tagSRxDesc -> next_desc type") ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: WARNING in rcu_check_gp_start_stall 2019-03-17 10:43 ` WARNING in rcu_check_gp_start_stall syzbot @ 2019-03-17 11:04 ` Greg KH 2019-03-18 12:18 ` Dmitry Vyukov 0 siblings, 1 reply; 3+ messages in thread From: Greg KH @ 2019-03-17 11:04 UTC (permalink / raw) To: syzbot Cc: bp, devel, douly.fnst, dvyukov, forest, hpa, konrad.wilk, len.brown, linux-kernel, linux-mm, mingo, peterz, puwen, syzkaller-bugs, tglx, tvboxspy, wang.yi59, x86 On Sun, Mar 17, 2019 at 03:43:01AM -0700, syzbot wrote: > syzbot has bisected this bug to: > > commit f1e3e92135202ff3d95195393ee62808c109208c > Author: Malcolm Priestley <tvboxspy@gmail.com> > Date: Wed Jul 22 18:16:42 2015 +0000 > > staging: vt6655: fix tagSRxDesc -> next_desc type > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=111856cf200000 > start commit: f1e3e921 staging: vt6655: fix tagSRxDesc -> next_desc type > git tree: upstream > final crash: https://syzkaller.appspot.com/x/report.txt?x=131856cf200000 > console output: https://syzkaller.appspot.com/x/log.txt?x=151856cf200000 > kernel config: https://syzkaller.appspot.com/x/.config?x=7132344728e7ec3f > dashboard link: https://syzkaller.appspot.com/bug?extid=111bc509cd9740d7e4aa > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16d4966cc00000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10c492d0c00000 > > Reported-by: syzbot+111bc509cd9740d7e4aa@syzkaller.appspotmail.com > Fixes: f1e3e921 ("staging: vt6655: fix tagSRxDesc -> next_desc type") I think syzbot is a bit confused here, how can this simple patch, where you do not have the hardware for this driver, cause this problem? thanks, greg k-h ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: WARNING in rcu_check_gp_start_stall 2019-03-17 11:04 ` Greg KH @ 2019-03-18 12:18 ` Dmitry Vyukov 0 siblings, 0 replies; 3+ messages in thread From: Dmitry Vyukov @ 2019-03-18 12:18 UTC (permalink / raw) To: Greg KH Cc: syzbot, Borislav Petkov, open list:ANDROID DRIVERS, Dou Liyang, forest, H. Peter Anvin, konrad.wilk, Len Brown, LKML, Linux-MM, Ingo Molnar, Peter Zijlstra, puwen, syzkaller-bugs, Thomas Gleixner, tvboxspy, wang.yi59, the arch/x86 maintainers On Sun, Mar 17, 2019 at 12:04 PM Greg KH <gregkh@linuxfoundation.org> wrote: > > On Sun, Mar 17, 2019 at 03:43:01AM -0700, syzbot wrote: > > syzbot has bisected this bug to: > > > > commit f1e3e92135202ff3d95195393ee62808c109208c > > Author: Malcolm Priestley <tvboxspy@gmail.com> > > Date: Wed Jul 22 18:16:42 2015 +0000 > > > > staging: vt6655: fix tagSRxDesc -> next_desc type > > > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=111856cf200000 > > start commit: f1e3e921 staging: vt6655: fix tagSRxDesc -> next_desc type > > git tree: upstream > > final crash: https://syzkaller.appspot.com/x/report.txt?x=131856cf200000 > > console output: https://syzkaller.appspot.com/x/log.txt?x=151856cf200000 > > kernel config: https://syzkaller.appspot.com/x/.config?x=7132344728e7ec3f > > dashboard link: https://syzkaller.appspot.com/bug?extid=111bc509cd9740d7e4aa > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16d4966cc00000 > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10c492d0c00000 > > > > Reported-by: syzbot+111bc509cd9740d7e4aa@syzkaller.appspotmail.com > > Fixes: f1e3e921 ("staging: vt6655: fix tagSRxDesc -> next_desc type") > > I think syzbot is a bit confused here, how can this simple patch, where > you do not have the hardware for this driver, cause this problem? Yes, I guess so. This perf_event_open+sched_setattr combo bug causes problems with hangs at random places, developers looking at these hangs again and again, incorrect bisection. I would be useful if somebody knowledgeable in perf/sched look at it. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-03-18 12:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <0000000000007da94e05827ea99a@google.com>
2019-03-17 10:43 ` WARNING in rcu_check_gp_start_stall syzbot
2019-03-17 11:04 ` Greg KH
2019-03-18 12:18 ` Dmitry Vyukov
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox