Re: [syzbot] [net?] INFO: task hung in new_device_store (5)

[Tetsuo Handa]

If we ratelimit

  "received packet on %s with own address as source address (addr:%pM, vlan:%u)\n",

message with up to once per 2 second [1], this problem is shown as "task hung in rtnl_lock".
If we ratelimit this message with up to 10 times per 5 second [2], this problem is shown as
"INFO: task hung in del_device_store".

This difference suggests that this task hung is caused by out of CPU time for making
forward progress due to spending too much CPU time for printk() operation from interrupt
context. We might want to ratelimit more aggressively.

Link: https://lkml.kernel.org/r/69533402.050a0220.329c0f.0428.GAE@xxxxxxxxxx [1]
Link: https://lkml.kernel.org/r/695347ee.050a0220.329c0f.042b.GAE@xxxxxxxxxx [2]