OpenVZ Forum


Home » Mailing lists » Devel » [PATCH] Set a separate lockdep class for neighbour table's proxy_queue
Re: [PATCH] Set a separate lockdep class for neighbour table's proxy_queue [message #12106 is a reply to message #12047] Tue, 17 April 2007 19:46 Go to previous messageGo to previous message
davem is currently offline  davem
Messages: 463
Registered: February 2006
Senior Member
From: Pavel Emelianov <xemul@sw.ru>
Date: Mon, 16 Apr 2007 16:08:25 +0400

> Otherwise the following calltrace will lead to a wrong
> lockdep warning:
>
> neigh_proxy_process()
> `- lock(neigh_table->proxy_queue.lock);
> arp_redo /* via tbl->proxy_redo */
> arp_process
> neigh_event_ns
> neigh_update
> skb_queue_purge
> `- lock(neighbor->arp_queue.lock);
>
> This is not a deadlock actually, as neighbor table's proxy_queue
> and the neighbor's arp_queue are different queues.
>
> Lockdep thinks there is a deadlock as both queues are initialized
> with skb_queue_head_init() and thus have a common class.

Patch applied, thank you.

Please provide a proper "Signed-off-by: " line in future patch
submissions or else I will ignore your patches entirely.

Thanks!
 
Read Message
Read Message
Read Message
Previous Topic: Re: [patch 05/10] add "permit user mounts in new namespace" clone flag
Next Topic: [PATCH] usbatm: Update to use the kthread api.
Goto Forum:
  


Current Time: Wed Sep 18 00:30:23 GMT 2024

Total time taken to generate the page: 0.04960 seconds