On Tue, 16 Nov 1999, Jorge Matias wrote:
> I don't know if anyone of you has this problem, but I found that
> everytime ax25d answers a call and spawns a connection to a service it
> opens "ax25" module for use. The problem is that when the connection is
> closed we still have the "ax25" module opened.
> This means that I can never remove ax25 module from memory because it
> says it is in use.
> When I made my last reboot I had ax25 module opened 725 times.
I investigated this last week and was able to come up with a possible
solution to the problem, which seems to be an oversight in the kernel
code.
Would people please test the attached patch to linux/net/ax25/af_ax25.c
(even if you haven't noticed any adverse effects or don't use modules at
all) and send success and/or failure reports to the list or directly to
me. Obvliously the patch is against 2.2.13.
For more details see the Dev-Hams list archives at
<http://www.hes.iki.fi/archive/dev-hams/>.
--
Tomi Manninen Internet: [EMAIL PROTECTED]
OH2BNS AX.25: [EMAIL PROTECTED]
KP20ME04 Amprnet: [EMAIL PROTECTED]
--- af_ax25.c.old Sun Oct 31 22:30:05 1999
+++ af_ax25.c Sat Dec 4 16:51:52 1999
@@ -1266,8 +1266,6 @@
newsk->sleep = &newsock->wait;
/* Now attach up the new socket */
- skb->sk = NULL;
- skb->destructor = NULL;
kfree_skb(skb);
sk->ack_backlog--;
newsock->sk = newsk;
