syzkaller triggers tremendous amounts of "unregister_netdevice: waiting for dev to become free" warnings: https://syzkaller.appspot.com/bug?id=949ecf93b67ab1df8f890571d24ef9db50872c96 The warning comes from: https://elixir.bootlin.com/linux/v5.11/source/net/core/dev.c#L10261 The warning is triggered after 10 seconds of waiting for the device to become free (all references are dropped). While 10 second wait generally should not happen in normal life (NETDEV_UNREGISTER notification should make everybody drop references), it seems to fire falsely very often during fuzzing. At least it's not possible to understand if it's really a false positive or not. All messages the same, so we can't e.g. detect only 10-th such message. We raise other stall/hang timeouts to 100-140 seconds and in qemu 3x more. 10 seconds is really too unreliable timeout. We used to ignore these messages entirely, but then real hangs are detected as unuseful "no output". We need to make this timeout configurable and/or fire a real WARNING after some timeout. If we keep "unregister_netdevice: waiting for dev to become free" message and add a WARNING, then we need to somehow change the message text, so that syzkaller does not consider it as bug anymore (while still considers the old message as bug on older kernels).
FTR mailed "net: make unregister netdev warning timeout configurable".
The patch was merged [1], this issue is resolved, right? [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa3afe107d9099fc0dea2acf82c3e3c8f0f20e2
Yes, +Eric's patches for debug refcounts in the net subsystem.