netdev - Re: "WARNING: CPU: 4 PID: 1 at ./include/net/genetlink.h:294 genlmsg_multicast_netns.isra.10.constprop.19+0x34/0x5e" with mlx4 under 4.9.137

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ea6a7867-d7a4-b2d8-1173-fcb2ad675bf7@ans.pl>
Date:   Sun, 18 Nov 2018 20:31:52 -0800
From:   Krzysztof Olędzki <ole@....pl>
To:     tariqt@...lanox.com, jiri@...lanox.com
Cc:     netdev@...r.kernel.org, johannes.berg@...el.com
Subject: Re: "WARNING: CPU: 4 PID: 1 at ./include/net/genetlink.h:294
 genlmsg_multicast_netns.isra.10.constprop.19+0x34/0x5e" with mlx4 under
 4.9.137

-> jiri@...lanox.com

> Hi,
> 
> I just upgraded kernel from 4.4.161 to 4.9.137 on one of my servers (Dell PowerEdge T110 II) and found this in the dmesg:
> 
> [    0.796066] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
> [    0.796251] ------------[ cut here ]------------
> [    0.796435] WARNING: CPU: 4 PID: 1 at ./include/net/genetlink.h:294 genlmsg_multicast_netns.isra.10.constprop.19+0x34/0x5e
> [    0.796724] CPU: 4 PID: 1 Comm: swapper/0 Not tainted 4.9.137-o2 #1
> [    0.796898] Hardware name: Dell Inc. PowerEdge T110 II/0PM2CW, BIOS 2.10.0 05/24/2018
> [    0.797188]  ffffc90000013c08 ffffffff813ea8f6 0000000000000000 0000000000000000
> [    0.797679]  ffffc90000013c48 ffffffff8110df65 0000012600000ec0 00000000ffffffea
> [    0.798157]  ffff88081a320000 0000000000000003 00000000fffffff4 ffffffff818eb360
> [    0.798648] Call Trace:
> [    0.798819]  [<ffffffff813ea8f6>] dump_stack+0x4f/0x65
> [    0.798993]  [<ffffffff8110df65>] __warn+0xce/0xe9
> [    0.799164]  [<ffffffff8110e028>] warn_slowpath_null+0x18/0x1a
> [    0.799343]  [<ffffffff81688b88>] genlmsg_multicast_netns.isra.10.constprop.19+0x34/0x5e
> [    0.799637]  [<ffffffff816890d5>] devlink_notify+0x54/0x5b
> [    0.799813]  [<ffffffff816896f7>] devlink_register+0x46/0x59
> [    0.799989]  [<ffffffff8155ef29>] mlx4_init_one+0x104/0x4c7
> [    0.800163]  [<ffffffff8112b4d6>] ? preempt_latency_start+0x21/0x57
> [    0.800341]  [<ffffffff8112d4e4>] ? preempt_count_add+0x70/0x73
> [    0.800515]  [<ffffffff814202db>] ? pci_match_id+0x32/0x57
> [    0.800689]  [<ffffffff81420739>] pci_device_probe+0x6e/0xb9
> [    0.800867]  [<ffffffff814cdd67>] driver_probe_device+0xf9/0x222
> [    0.804465]  [<ffffffff814cdefd>] __driver_attach+0x6d/0x8f
> [    0.804638]  [<ffffffff814cde90>] ? driver_probe_device+0x222/0x222
> [    0.804814]  [<ffffffff814cc5e8>] bus_for_each_dev+0x6a/0x82
> [    0.804988]  [<ffffffff814ce0df>] driver_attach+0x19/0x1b
> [    0.805164]  [<ffffffff814ccd96>] bus_add_driver+0xee/0x1c9
> [    0.805342]  [<ffffffff81d486df>] ? do_early_param+0x90/0x90
> [    0.805519]  [<ffffffff814ce502>] driver_register+0x83/0xba
> [    0.805689]  [<ffffffff81d90724>] ? tg3_driver_init+0x1b/0x1b
> [    0.805862]  [<ffffffff8142058d>] __pci_register_driver+0x44/0x46
> [    0.806034]  [<ffffffff81d9082d>] mlx4_init+0x109/0x12a
> [    0.806200]  [<ffffffff81d90724>] ? tg3_driver_init+0x1b/0x1b
> [    0.806377]  [<ffffffff81d48efb>] do_one_initcall+0x8b/0x10e
> [    0.806547]  [<ffffffff81d486df>] ? do_early_param+0x90/0x90
> [    0.806717]  [<ffffffff81d490cf>] kernel_init_freeable+0x151/0x1dd
> [    0.806890]  [<ffffffff817dbe16>] ? rest_init+0x7d/0x7d
> [    0.807061]  [<ffffffff817dbe1f>] kernel_init+0x9/0x105
> [    0.807232]  [<ffffffff817e01d4>] ret_from_fork+0x54/0x60
> [    0.807415] ---[ end trace 34e550e5d3d83d0a ]---
> [    0.807582] mlx4_core: Initializing 0000:01:00.0
> 
> The NIC seems to work correctly, but the warning appears after each boot.
> There is also BCM5722 (tg3) NIC in the system. The only thing that changes
> between boots is the CPU reported in the message.
> 
> I can try bisec or test a more recent kernel, but this will have to wait after
> I come back from my Thanksgiving travel.
> 
> $ lspci -nn shows:
> 01:00.0 Ethernet controller [0200]: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] [15b3:6750] (rev b0)
> 
> Thanks,
>   Krzysztof
>