Re: [PATCH] Set a separate lockdep class for neighbour table's proxy_queue

2007-04-19 Thread Jarek Poplawski
On 17-04-2007 21:46, David Miller wrote: > From: Pavel Emelianov <[EMAIL PROTECTED]> > 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 /*

Re: [PATCH] Set a separate lockdep class for neighbour table's proxy_queue

2007-04-17 Thread David Miller
From: Pavel Emelianov <[EMAIL PROTECTED]> 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_ev

[PATCH] Set a separate lockdep class for neighbour table's proxy_queue

2007-04-16 Thread Pavel Emelianov
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 dea