summaryrefslogtreecommitdiff
path: root/net/ax25/Kconfig
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2008-06-17 21:26:37 -0700
committerDavid S. Miller <davem@davemloft.net>2008-06-17 21:26:37 -0700
commit30902dc3cb0ea1cfc7ac2b17bcf478ff98420d74 (patch)
tree67f71e024ca0e2f0bf2afceb82444297679836e1 /net/ax25/Kconfig
parent9d45abe1c2949183e5d9cb25721bf1c42c7b5e3b (diff)
ax25: Fix std timer socket destroy handling.
Tihomir Heidelberg - 9a4gl, reports: -------------------- I would like to direct you attention to one problem existing in ax.25 kernel since 2.4. If listening socket is closed and its SKB queue is released but those sockets get weird. Those "unAccepted()" sockets should be destroyed in ax25_std_heartbeat_expiry, but it will not happen. And there is also a note about that in ax25_std_timer.c: /* Magic here: If we listen() and a new link dies before it is accepted() it isn't 'dead' so doesn't get removed. */ This issue cause ax25d to stop accepting new connections and I had to restarted ax25d approximately each day and my services were unavailable. Also netstat -n -l shows invalid source and device for those listening sockets. It is strange why ax25d's listening socket get weird because of this issue, but definitely when I solved this bug I do not have problems with ax25d anymore and my ax25d can run for months without problems. -------------------- Actually as far as I can see, this problem is even in releases as far back as 2.2.x as well. It seems senseless to special case this test on TCP_LISTEN state. Anything still stuck in state 0 has no external references and we can just simply kill it off directly. Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ax25/Kconfig')
0 files changed, 0 insertions, 0 deletions