Thread (8 messages) 8 messages, 3 authors, 2005-05-30

Re: [PATCH 2.6] fix deadlock with ip_queue and tcp local input path

From: "David S. Miller" <davem@davemloft.net>
Date: 2005-05-26 21:01:57
Also in: netfilter-devel

From: Harald Welte <redacted>
Subject: Re: [PATCH 2.6] fix deadlock with ip_queue and tcp local input path
Date: Thu, 26 May 2005 22:58:31 +0200
On Thu, May 26, 2005 at 01:52:29PM -0700, David S. Miller wrote:
 
quoted
quoted
Dave: Please don't apply yet, I want to receive feedback from the
netfilter developers first.  I'm just Cc'ing netdev in case somebody
wants an intermediate fix to fix the problem.
OK.
Do you have any feedback on why or how bh_lock_sock() might be called in
the problem I've described?  I think it has to be a different skb for
the same socket.
When we hit a listening socket, and hung off of that listening
socket we find a child socket, we bh_lock_sock() the child socket
then process the SKB against it instead of the listening socket.

Is this the kind of scenerio you are concerned about?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help