On Wed, December 13, 2006 1:29 am, David Miller said:
I think we're still not onto the right fix.
I took a look, and the issue seems to simply be that the
__tcp_put_md5sig_pool() is not doing the reference count
thing that __tcp_get_md5sig_pool() does (via tcp_md5sig_users).
The direct call
From: Leigh Brown [EMAIL PROTECTED]
Date: Wed, 13 Dec 2006 23:43:50 - (GMT)
I just had to kill the parameter:-
--- net/ipv4/tcp.c.orig 2006-12-10 21:46:26.0 +
+++ net/ipv4/tcp.c2006-12-13 17:38:29.0 +
@@ -2362,7 +2362,7 @@ struct tcp_md5sig_pool
From: Leigh Brown [EMAIL PROTECTED]
Date: Tue, 12 Dec 2006 23:03:34 - (GMT)
Well, the inline functions seem okay in that regard, but I'll bow to
your superior judgement.
I think we're still not onto the right fix.
I took a look, and the issue seems to simply be that the
Hello,
I decided to try out the md5 signature support, with a view to eventually
fixing up Quagga to make use of it. As the API has changed quite a bit,
I modified a simple echo client/server as a simple test. I compiled
up 2.6.19-git17 and ran it under debian etch.
Unfortunately, both the
