> On Apr 18, 2020, at 3:02 AM, Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote: > > On Sat, Mar 14, 2020 at 8:57 AM syzbot > <syzbot+7ef50afd3a211f879112@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: >> >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit: 2e602db7 Add linux-next specific files for 20200313 >> git tree: linux-next >> console output: https://syzkaller.appspot.com/x/log.txt?x=16669919e00000 >> kernel config: https://syzkaller.appspot.com/x/.config?x=cf2879fc1055b886 >> dashboard link: https://syzkaller.appspot.com/bug?extid=7ef50afd3a211f879112 >> compiler: gcc (GCC) 9.0.0 20181231 (experimental) >> >> Unfortunately, I don't have any reproducer for this crash yet. >> >> IMPORTANT: if you fix the bug, please add the following tag to the commit: >> Reported-by: syzbot+7ef50afd3a211f879112@xxxxxxxxxxxxxxxxxxxxxxxxx > > +linux-next, Stephen for currently open linux-next build/boot failure > >> ============================= >> WARNING: suspicious RCU usage >> 5.6.0-rc5-next-20200313-syzkaller #0 Not tainted >> ----------------------------- >> net/openvswitch/conntrack.c:1898 RCU-list traversed in non-reader section! Those should be fixed by, https://lore.kernel.org/netdev/1587063451-54027-1-git-send-email-xiangxia.m.yue@xxxxxxxxx/ >> ============================= >> WARNING: suspicious RCU usage >> 5.6.0-rc5-next-20200313-syzkaller #0 Not tainted >> ----------------------------- >> net/ipv4/ipmr.c:1757 RCU-list traversed in non-reader section!! and, https://lore.kernel.org/netdev/20200222063835.14328-1-frextrite@xxxxxxxxx/ It looks like both are waiting for David to pick up.
