Commits
Pavel Emelianov authored 958955c928e
[LOCKDEP] Fix wrong deadlock report in neigh table Lockdep detects a fake deadlock in the calltrace: neigh_proxy_process() `- lock(neigh_table->proxy_queue.lock); arp_process (tbl->proxy_redo) neigh_event_ns neigh_update skb_purge_queue `- lock(neighbour->arp_queue.lock); Actually there is no deadlock as the first lock and the second one are different skb_buff_head's locks, but they are initialized both in skb_queue_head_init() and thus have on lockdep-class. This is a mainstream "BUG". Fixed by adding another class to neigh_table's proxy_queue lock. (Tested with node bootup, VE start and vzt-prep vzt-ss).