Re: linux-next boot error: WARNING: suspicious RCU usage in ip6mr_get_table
On Tue, May 12, 2020 at 11:28:47AM +1000, Stephen Rothwell wrote: > Hi all, > > On Fri, 8 May 2020 04:54:02 +0530 Madhuparna Bhowmik > wrote: > > > > On Thu, May 07, 2020 at 08:50:55AM -0400, Qian Cai wrote: > > > > > > > > > > On May 7, 2020, at 5:32 AM, Dmitry Vyukov wrote: > > > > > > > > On Thu, May 7, 2020 at 11:26 AM syzbot > > > > wrote: > > > >> > > > >> Hello, > > > >> > > > >> syzbot found the following crash on: > > > >> > > > >> HEAD commit:6b43f715 Add linux-next specific files for 20200507 > > > >> git tree: linux-next > > > >> console output: > > > >> https://syzkaller.appspot.com/x/log.txt?x=16f6437010 > > > >> kernel config: > > > >> https://syzkaller.appspot.com/x/.config?x=ef9b7a80b923f328 > > > >> dashboard link: > > > >> https://syzkaller.appspot.com/bug?extid=761cff389b454aa387d2 > > > >> 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+761cff389b454aa38...@syzkaller.appspotmail.com > > > > > > > > > > > > +linux-next for linux-next boot breakage > > > > > > Amol, Madhuparna, Is either of you still working on this? > > > > > > >> = > > > >> WARNING: suspicious RCU usage > > > >> 5.7.0-rc4-next-20200507-syzkaller #0 Not tainted > > > >> - > > > >> net/ipv6/ip6mr.c:124 RCU-list traversed in non-reader section!! > > > >> > > I had some doubt in this one, I have already mailed the maintainers, > > waiting for their reply. > > This is blocking syzbot testing of linux-next ... are we getting > anywhere? Will a patch similar to the ipmr.c one help here? > Hi Stephen, There are some discussions going on about the ipmr.c patch, I guess even ip6mr can be fixed in a similar way. Let me still confirm once. Thank you, Mahuparna > -- > Cheers, > Stephen Rothwell
Re: linux-next boot error: WARNING: suspicious RCU usage in ip6mr_get_table
Hi all, On Fri, 8 May 2020 04:54:02 +0530 Madhuparna Bhowmik wrote: > > On Thu, May 07, 2020 at 08:50:55AM -0400, Qian Cai wrote: > > > > > > > On May 7, 2020, at 5:32 AM, Dmitry Vyukov wrote: > > > > > > On Thu, May 7, 2020 at 11:26 AM syzbot > > > wrote: > > >> > > >> Hello, > > >> > > >> syzbot found the following crash on: > > >> > > >> HEAD commit:6b43f715 Add linux-next specific files for 20200507 > > >> git tree: linux-next > > >> console output: https://syzkaller.appspot.com/x/log.txt?x=16f6437010 > > >> kernel config: > > >> https://syzkaller.appspot.com/x/.config?x=ef9b7a80b923f328 > > >> dashboard link: > > >> https://syzkaller.appspot.com/bug?extid=761cff389b454aa387d2 > > >> 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+761cff389b454aa38...@syzkaller.appspotmail.com > > > > > > > > > +linux-next for linux-next boot breakage > > > > Amol, Madhuparna, Is either of you still working on this? > > > > >> = > > >> WARNING: suspicious RCU usage > > >> 5.7.0-rc4-next-20200507-syzkaller #0 Not tainted > > >> - > > >> net/ipv6/ip6mr.c:124 RCU-list traversed in non-reader section!! > > >> > I had some doubt in this one, I have already mailed the maintainers, > waiting for their reply. This is blocking syzbot testing of linux-next ... are we getting anywhere? Will a patch similar to the ipmr.c one help here? -- Cheers, Stephen Rothwell pgp9SXvN1VQmV.pgp Description: OpenPGP digital signature
Re: linux-next boot error: WARNING: suspicious RCU usage in ip6mr_get_table
Hi Madhuparna, On Fri, 8 May 2020 04:54:02 +0530 Madhuparna Bhowmik wrote: > > On Thu, May 07, 2020 at 08:50:55AM -0400, Qian Cai wrote: > > > > > > > On May 7, 2020, at 5:32 AM, Dmitry Vyukov wrote: > > > > > > On Thu, May 7, 2020 at 11:26 AM syzbot > > > wrote: > > >> > > >> = > > >> WARNING: suspicious RCU usage > > >> 5.7.0-rc4-next-20200507-syzkaller #0 Not tainted > > >> - > > >> security/integrity/evm/evm_main.c:231 RCU-list traversed in non-reader > > >> section!! > > >> > Here is the patch for this one: > https://lore.kernel.org/patchwork/patch/1233836/ Thanks, I will apply that one to linux-next today. -- Cheers, Stephen Rothwell pgpLMZyD4wSzg.pgp Description: OpenPGP digital signature
Re: linux-next boot error: WARNING: suspicious RCU usage in ip6mr_get_table
On Thu, May 07, 2020 at 08:50:55AM -0400, Qian Cai wrote:
>
>
> > On May 7, 2020, at 5:32 AM, Dmitry Vyukov wrote:
> >
> > On Thu, May 7, 2020 at 11:26 AM syzbot
> > wrote:
> >>
> >> Hello,
> >>
> >> syzbot found the following crash on:
> >>
> >> HEAD commit:6b43f715 Add linux-next specific files for 20200507
> >> git tree: linux-next
> >> console output: https://syzkaller.appspot.com/x/log.txt?x=16f6437010
> >> kernel config: https://syzkaller.appspot.com/x/.config?x=ef9b7a80b923f328
> >> dashboard link:
> >> https://syzkaller.appspot.com/bug?extid=761cff389b454aa387d2
> >> 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+761cff389b454aa38...@syzkaller.appspotmail.com
> >
> >
> > +linux-next for linux-next boot breakage
>
> Amol, Madhuparna, Is either of you still working on this?
>
> >
> >> SoftiWARP attached
> >> Driver 'framebuffer' was unable to register with bus_type 'coreboot'
> >> because the bus was not initialized.
> >> Driver 'memconsole' was unable to register with bus_type 'coreboot'
> >> because the bus was not initialized.
> >> Driver 'vpd' was unable to register with bus_type 'coreboot' because the
> >> bus was not initialized.
> >> hid: raw HID events driver (C) Jiri Kosina
> >> usbcore: registered new interface driver usbhid
> >> usbhid: USB HID core driver
> >> ashmem: initialized
> >> usbcore: registered new interface driver snd-usb-audio
> >> drop_monitor: Initializing network drop monitor service
> >> NET: Registered protocol family 26
> >> GACT probability on
> >> Mirror/redirect action on
> >> Simple TC action Loaded
> >> netem: version 1.3
> >> u32 classifier
> >>Performance counters on
> >>input device check on
> >>Actions configured
> >> nf_conntrack_irc: failed to register helpers
> >> nf_conntrack_sane: failed to register helpers
> >> nf_conntrack_sip: failed to register helpers
> >> xt_time: kernel timezone is -
> >> IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
> >> IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
> >> IPVS: ipvs loaded.
> >> IPVS: [rr] scheduler registered.
> >> IPVS: [wrr] scheduler registered.
> >> IPVS: [lc] scheduler registered.
> >> IPVS: [wlc] scheduler registered.
> >> IPVS: [fo] scheduler registered.
> >> IPVS: [ovf] scheduler registered.
> >> IPVS: [lblc] scheduler registered.
> >> IPVS: [lblcr] scheduler registered.
> >> IPVS: [dh] scheduler registered.
> >> IPVS: [sh] scheduler registered.
> >> IPVS: [mh] scheduler registered.
> >> IPVS: [sed] scheduler registered.
> >> IPVS: [nq] scheduler registered.
> >> IPVS: ftp: loaded support on port[0] = 21
> >> IPVS: [sip] pe registered.
> >> ipip: IPv4 and MPLS over IPv4 tunneling driver
> >> gre: GRE over IPv4 demultiplexor driver
> >> ip_gre: GRE over IPv4 tunneling driver
> >> IPv4 over IPsec tunneling driver
> >> ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
> >> Initializing XFRM netlink socket
> >> IPsec XFRM device driver
> >> NET: Registered protocol family 10
> >> =
> >> WARNING: suspicious RCU usage
> >> 5.7.0-rc4-next-20200507-syzkaller #0 Not tainted
> >> -
> >> net/ipv6/ip6mr.c:124 RCU-list traversed in non-reader section!!
> >>
I had some doubt in this one, I have already mailed the maintainers,
waiting for their reply.
> >> other info that might help us debug this:
> >>
> >>
> >> rcu_scheduler_active = 2, debug_locks = 1
> >> 1 lock held by swapper/0/1:
> >> #0: 8a7aae30 (pernet_ops_rwsem){+.+.}-{3:3}, at:
> >> register_pernet_subsys+0x16/0x40 net/core/net_namespace.c:1257
> >>
> >> stack backtrace:
> >> CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> >> 5.7.0-rc4-next-20200507-syzkaller #0
> >> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> >> Google 01/01/2011
> >> Call Trace:
> >> __dump_stack lib/dump_stack.c:77 [inline]
> >> dump_stack+0x18f/0x20d lib/dump_stack.c:118
> >> ip6mr_get_table+0x153/0x180 net/ipv6/ip6mr.c:124
> >> ip6mr_new_table+0x1b/0x70 net/ipv6/ip6mr.c:382
> >> ip6mr_rules_init net/ipv6/ip6mr.c:236 [inline]
> >> ip6mr_net_init+0x133/0x3f0 net/ipv6/ip6mr.c:1310
> >> ops_init+0xaf/0x420 net/core/net_namespace.c:151
> >> __register_pernet_operations net/core/net_namespace.c:1140 [inline]
> >> register_pernet_operations+0x346/0x840 net/core/net_namespace.c:1217
> >> register_pernet_subsys+0x25/0x40 net/core/net_namespace.c:1258
> >> ip6_mr_init+0x49/0x152 net/ipv6/ip6mr.c:1363
> >> inet6_init+0x1d7/0x6dc net/ipv6/af_inet6.c:1037
> >> do_one_initcall+0x10a/0x7d0 init/main.c:1159
> >> do_initcall_level init/main.c:1232 [inline]
> >> do_initcalls init/main.c:1248 [inline]
> >> do_basic_setup init/main.c:1268 [inline]
> >> kernel_init_freeable+0x501/0x5ae init/main.c:1454
> >> kernel_init+0xd/0x1bb
Re: linux-next boot error: WARNING: suspicious RCU usage in ip6mr_get_table
> On May 7, 2020, at 5:32 AM, Dmitry Vyukov wrote:
>
> On Thu, May 7, 2020 at 11:26 AM syzbot
> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:6b43f715 Add linux-next specific files for 20200507
>> git tree: linux-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=16f6437010
>> kernel config: https://syzkaller.appspot.com/x/.config?x=ef9b7a80b923f328
>> dashboard link: https://syzkaller.appspot.com/bug?extid=761cff389b454aa387d2
>> 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+761cff389b454aa38...@syzkaller.appspotmail.com
>
>
> +linux-next for linux-next boot breakage
Amol, Madhuparna, Is either of you still working on this?
>
>> SoftiWARP attached
>> Driver 'framebuffer' was unable to register with bus_type 'coreboot' because
>> the bus was not initialized.
>> Driver 'memconsole' was unable to register with bus_type 'coreboot' because
>> the bus was not initialized.
>> Driver 'vpd' was unable to register with bus_type 'coreboot' because the bus
>> was not initialized.
>> hid: raw HID events driver (C) Jiri Kosina
>> usbcore: registered new interface driver usbhid
>> usbhid: USB HID core driver
>> ashmem: initialized
>> usbcore: registered new interface driver snd-usb-audio
>> drop_monitor: Initializing network drop monitor service
>> NET: Registered protocol family 26
>> GACT probability on
>> Mirror/redirect action on
>> Simple TC action Loaded
>> netem: version 1.3
>> u32 classifier
>>Performance counters on
>>input device check on
>>Actions configured
>> nf_conntrack_irc: failed to register helpers
>> nf_conntrack_sane: failed to register helpers
>> nf_conntrack_sip: failed to register helpers
>> xt_time: kernel timezone is -
>> IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
>> IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
>> IPVS: ipvs loaded.
>> IPVS: [rr] scheduler registered.
>> IPVS: [wrr] scheduler registered.
>> IPVS: [lc] scheduler registered.
>> IPVS: [wlc] scheduler registered.
>> IPVS: [fo] scheduler registered.
>> IPVS: [ovf] scheduler registered.
>> IPVS: [lblc] scheduler registered.
>> IPVS: [lblcr] scheduler registered.
>> IPVS: [dh] scheduler registered.
>> IPVS: [sh] scheduler registered.
>> IPVS: [mh] scheduler registered.
>> IPVS: [sed] scheduler registered.
>> IPVS: [nq] scheduler registered.
>> IPVS: ftp: loaded support on port[0] = 21
>> IPVS: [sip] pe registered.
>> ipip: IPv4 and MPLS over IPv4 tunneling driver
>> gre: GRE over IPv4 demultiplexor driver
>> ip_gre: GRE over IPv4 tunneling driver
>> IPv4 over IPsec tunneling driver
>> ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
>> Initializing XFRM netlink socket
>> IPsec XFRM device driver
>> NET: Registered protocol family 10
>> =
>> WARNING: suspicious RCU usage
>> 5.7.0-rc4-next-20200507-syzkaller #0 Not tainted
>> -
>> net/ipv6/ip6mr.c:124 RCU-list traversed in non-reader section!!
>>
>> other info that might help us debug this:
>>
>>
>> rcu_scheduler_active = 2, debug_locks = 1
>> 1 lock held by swapper/0/1:
>> #0: 8a7aae30 (pernet_ops_rwsem){+.+.}-{3:3}, at:
>> register_pernet_subsys+0x16/0x40 net/core/net_namespace.c:1257
>>
>> stack backtrace:
>> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.7.0-rc4-next-20200507-syzkaller
>> #0
>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
>> Google 01/01/2011
>> Call Trace:
>> __dump_stack lib/dump_stack.c:77 [inline]
>> dump_stack+0x18f/0x20d lib/dump_stack.c:118
>> ip6mr_get_table+0x153/0x180 net/ipv6/ip6mr.c:124
>> ip6mr_new_table+0x1b/0x70 net/ipv6/ip6mr.c:382
>> ip6mr_rules_init net/ipv6/ip6mr.c:236 [inline]
>> ip6mr_net_init+0x133/0x3f0 net/ipv6/ip6mr.c:1310
>> ops_init+0xaf/0x420 net/core/net_namespace.c:151
>> __register_pernet_operations net/core/net_namespace.c:1140 [inline]
>> register_pernet_operations+0x346/0x840 net/core/net_namespace.c:1217
>> register_pernet_subsys+0x25/0x40 net/core/net_namespace.c:1258
>> ip6_mr_init+0x49/0x152 net/ipv6/ip6mr.c:1363
>> inet6_init+0x1d7/0x6dc net/ipv6/af_inet6.c:1037
>> do_one_initcall+0x10a/0x7d0 init/main.c:1159
>> do_initcall_level init/main.c:1232 [inline]
>> do_initcalls init/main.c:1248 [inline]
>> do_basic_setup init/main.c:1268 [inline]
>> kernel_init_freeable+0x501/0x5ae init/main.c:1454
>> kernel_init+0xd/0x1bb init/main.c:1359
>> ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:351
>> Segment Routing with IPv6
>> mip6: Mobile IPv6
>> sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
>> ip6_gre: GRE over IPv6 tunneling driver
>> NET: Registered protocol family 17
>> NET: Registered protocol family 15
>> Bridge firewalling registered
>> NET: Registered protocol family 9
>> X25: Linux Version 0.2
>> NET:
Re: linux-next boot error: WARNING: suspicious RCU usage in ip6mr_get_table
On Thu, May 7, 2020 at 11:26 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:6b43f715 Add linux-next specific files for 20200507
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=16f6437010
> kernel config: https://syzkaller.appspot.com/x/.config?x=ef9b7a80b923f328
> dashboard link: https://syzkaller.appspot.com/bug?extid=761cff389b454aa387d2
> 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+761cff389b454aa38...@syzkaller.appspotmail.com
+linux-next for linux-next boot breakage
> SoftiWARP attached
> Driver 'framebuffer' was unable to register with bus_type 'coreboot' because
> the bus was not initialized.
> Driver 'memconsole' was unable to register with bus_type 'coreboot' because
> the bus was not initialized.
> Driver 'vpd' was unable to register with bus_type 'coreboot' because the bus
> was not initialized.
> hid: raw HID events driver (C) Jiri Kosina
> usbcore: registered new interface driver usbhid
> usbhid: USB HID core driver
> ashmem: initialized
> usbcore: registered new interface driver snd-usb-audio
> drop_monitor: Initializing network drop monitor service
> NET: Registered protocol family 26
> GACT probability on
> Mirror/redirect action on
> Simple TC action Loaded
> netem: version 1.3
> u32 classifier
> Performance counters on
> input device check on
> Actions configured
> nf_conntrack_irc: failed to register helpers
> nf_conntrack_sane: failed to register helpers
> nf_conntrack_sip: failed to register helpers
> xt_time: kernel timezone is -
> IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
> IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
> IPVS: ipvs loaded.
> IPVS: [rr] scheduler registered.
> IPVS: [wrr] scheduler registered.
> IPVS: [lc] scheduler registered.
> IPVS: [wlc] scheduler registered.
> IPVS: [fo] scheduler registered.
> IPVS: [ovf] scheduler registered.
> IPVS: [lblc] scheduler registered.
> IPVS: [lblcr] scheduler registered.
> IPVS: [dh] scheduler registered.
> IPVS: [sh] scheduler registered.
> IPVS: [mh] scheduler registered.
> IPVS: [sed] scheduler registered.
> IPVS: [nq] scheduler registered.
> IPVS: ftp: loaded support on port[0] = 21
> IPVS: [sip] pe registered.
> ipip: IPv4 and MPLS over IPv4 tunneling driver
> gre: GRE over IPv4 demultiplexor driver
> ip_gre: GRE over IPv4 tunneling driver
> IPv4 over IPsec tunneling driver
> ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
> Initializing XFRM netlink socket
> IPsec XFRM device driver
> NET: Registered protocol family 10
> =
> WARNING: suspicious RCU usage
> 5.7.0-rc4-next-20200507-syzkaller #0 Not tainted
> -
> net/ipv6/ip6mr.c:124 RCU-list traversed in non-reader section!!
>
> other info that might help us debug this:
>
>
> rcu_scheduler_active = 2, debug_locks = 1
> 1 lock held by swapper/0/1:
> #0: 8a7aae30 (pernet_ops_rwsem){+.+.}-{3:3}, at:
> register_pernet_subsys+0x16/0x40 net/core/net_namespace.c:1257
>
> stack backtrace:
> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.7.0-rc4-next-20200507-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> Call Trace:
> __dump_stack lib/dump_stack.c:77 [inline]
> dump_stack+0x18f/0x20d lib/dump_stack.c:118
> ip6mr_get_table+0x153/0x180 net/ipv6/ip6mr.c:124
> ip6mr_new_table+0x1b/0x70 net/ipv6/ip6mr.c:382
> ip6mr_rules_init net/ipv6/ip6mr.c:236 [inline]
> ip6mr_net_init+0x133/0x3f0 net/ipv6/ip6mr.c:1310
> ops_init+0xaf/0x420 net/core/net_namespace.c:151
> __register_pernet_operations net/core/net_namespace.c:1140 [inline]
> register_pernet_operations+0x346/0x840 net/core/net_namespace.c:1217
> register_pernet_subsys+0x25/0x40 net/core/net_namespace.c:1258
> ip6_mr_init+0x49/0x152 net/ipv6/ip6mr.c:1363
> inet6_init+0x1d7/0x6dc net/ipv6/af_inet6.c:1037
> do_one_initcall+0x10a/0x7d0 init/main.c:1159
> do_initcall_level init/main.c:1232 [inline]
> do_initcalls init/main.c:1248 [inline]
> do_basic_setup init/main.c:1268 [inline]
> kernel_init_freeable+0x501/0x5ae init/main.c:1454
> kernel_init+0xd/0x1bb init/main.c:1359
> ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:351
> Segment Routing with IPv6
> mip6: Mobile IPv6
> sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
> ip6_gre: GRE over IPv6 tunneling driver
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> Bridge firewalling registered
> NET: Registered protocol family 9
> X25: Linux Version 0.2
> NET: Registered protocol family 6
> NET: Registered protocol family 11
> NET: Registered protocol family 3
> can: controller area network core (rev 20170425 abi 9)
> NET: Registered protocol family 29
> can: raw protocol (rev 20170425)
> can:
linux-next boot error: WARNING: suspicious RCU usage in ip6mr_get_table
Hello,
syzbot found the following crash on:
HEAD commit:6b43f715 Add linux-next specific files for 20200507
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16f6437010
kernel config: https://syzkaller.appspot.com/x/.config?x=ef9b7a80b923f328
dashboard link: https://syzkaller.appspot.com/bug?extid=761cff389b454aa387d2
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+761cff389b454aa38...@syzkaller.appspotmail.com
SoftiWARP attached
Driver 'framebuffer' was unable to register with bus_type 'coreboot' because
the bus was not initialized.
Driver 'memconsole' was unable to register with bus_type 'coreboot' because the
bus was not initialized.
Driver 'vpd' was unable to register with bus_type 'coreboot' because the bus
was not initialized.
hid: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ashmem: initialized
usbcore: registered new interface driver snd-usb-audio
drop_monitor: Initializing network drop monitor service
NET: Registered protocol family 26
GACT probability on
Mirror/redirect action on
Simple TC action Loaded
netem: version 1.3
u32 classifier
Performance counters on
input device check on
Actions configured
nf_conntrack_irc: failed to register helpers
nf_conntrack_sane: failed to register helpers
nf_conntrack_sip: failed to register helpers
xt_time: kernel timezone is -
IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
IPVS: ipvs loaded.
IPVS: [rr] scheduler registered.
IPVS: [wrr] scheduler registered.
IPVS: [lc] scheduler registered.
IPVS: [wlc] scheduler registered.
IPVS: [fo] scheduler registered.
IPVS: [ovf] scheduler registered.
IPVS: [lblc] scheduler registered.
IPVS: [lblcr] scheduler registered.
IPVS: [dh] scheduler registered.
IPVS: [sh] scheduler registered.
IPVS: [mh] scheduler registered.
IPVS: [sed] scheduler registered.
IPVS: [nq] scheduler registered.
IPVS: ftp: loaded support on port[0] = 21
IPVS: [sip] pe registered.
ipip: IPv4 and MPLS over IPv4 tunneling driver
gre: GRE over IPv4 demultiplexor driver
ip_gre: GRE over IPv4 tunneling driver
IPv4 over IPsec tunneling driver
ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
Initializing XFRM netlink socket
IPsec XFRM device driver
NET: Registered protocol family 10
=
WARNING: suspicious RCU usage
5.7.0-rc4-next-20200507-syzkaller #0 Not tainted
-
net/ipv6/ip6mr.c:124 RCU-list traversed in non-reader section!!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1
1 lock held by swapper/0/1:
#0: 8a7aae30 (pernet_ops_rwsem){+.+.}-{3:3}, at:
register_pernet_subsys+0x16/0x40 net/core/net_namespace.c:1257
stack backtrace:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.7.0-rc4-next-20200507-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google
01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x18f/0x20d lib/dump_stack.c:118
ip6mr_get_table+0x153/0x180 net/ipv6/ip6mr.c:124
ip6mr_new_table+0x1b/0x70 net/ipv6/ip6mr.c:382
ip6mr_rules_init net/ipv6/ip6mr.c:236 [inline]
ip6mr_net_init+0x133/0x3f0 net/ipv6/ip6mr.c:1310
ops_init+0xaf/0x420 net/core/net_namespace.c:151
__register_pernet_operations net/core/net_namespace.c:1140 [inline]
register_pernet_operations+0x346/0x840 net/core/net_namespace.c:1217
register_pernet_subsys+0x25/0x40 net/core/net_namespace.c:1258
ip6_mr_init+0x49/0x152 net/ipv6/ip6mr.c:1363
inet6_init+0x1d7/0x6dc net/ipv6/af_inet6.c:1037
do_one_initcall+0x10a/0x7d0 init/main.c:1159
do_initcall_level init/main.c:1232 [inline]
do_initcalls init/main.c:1248 [inline]
do_basic_setup init/main.c:1268 [inline]
kernel_init_freeable+0x501/0x5ae init/main.c:1454
kernel_init+0xd/0x1bb init/main.c:1359
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:351
Segment Routing with IPv6
mip6: Mobile IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
ip6_gre: GRE over IPv6 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
Bridge firewalling registered
NET: Registered protocol family 9
X25: Linux Version 0.2
NET: Registered protocol family 6
NET: Registered protocol family 11
NET: Registered protocol family 3
can: controller area network core (rev 20170425 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20170425)
can: broadcast manager protocol (rev 20170425 t)
can: netlink gateway (rev 20190810) max_hops=1
can: SAE J1939
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket
