Hi,
It's nice to have no more kernel panic, thanks to Basil Gunn's AX.25 recently applied patch. However, an issue remains when an AX.25 connection fails or after disconnecting from a remote station. /proc/net/ax25 remains populated by a number of entries forever as shown here : [root@f6bvp-6 bernard]# cat /proc/net/ax25 ffff8c80b5ed6c00 ax0 TM6BVP-1 FE6BVP-1 1 0 0 0 15 50 0 3 0 300 0 0 4 10 5 2 256 0 0 18495 ffff8c80b5ed6400 ax0 TM6BVP-1 F6BVP-1 1 0 0 0 15 50 0 3 0 300 0 0 4 10 5 2 256 0 0 18493 ffff8c80b5ef5800 ax0 F6BVP-6 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18299 ffff8c80b5ef6000 ax0 TM6BVP-1 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18296 ffff8c80b5ed7400 ax0 TM6BVP-1 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18472 ffff8c80b5ed5800 ax0 F6BVP-7 F4BWT-9 1 0 0 0 1 60 0 3 0 300 0 0 5 10 5 2 256 * * * ffff8c80b5ed5400 ax0 F6BVP-7 WA3MEZ-9 1 0 0 0 1 60 0 3 0 300 0 0 5 10 5 2 256 * * * [root@f6bvp-6 bernard]# cat /proc/net/ax25 ffff8c80b5ed6c00 ax0 TM6BVP-1 FE6BVP-1 1 0 0 0 14 50 0 3 0 300 0 0 4 10 5 2 256 0 0 18495 ffff8c80b5ed6400 ax0 TM6BVP-1 F6BVP-1 1 0 0 0 14 50 0 3 0 300 0 0 4 10 5 2 256 0 0 18493 ffff8c80b5ef5800 ax0 F6BVP-6 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18299 ffff8c80b5ef6000 ax0 TM6BVP-1 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18296 ffff8c80b5ed7400 ax0 TM6BVP-1 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18472 ffff8c80b5ed5800 ax0 F6BVP-7 F4BWT-9 1 0 0 0 0 60 0 3 0 300 0 0 5 10 5 2 256 * * * ffff8c80b5ed5400 ax0 F6BVP-7 WA3MEZ-9 1 0 0 0 0 60 0 3 0 300 0 0 5 10 5 2 256 * * * [root@f6bvp-6 bernard]# cat /proc/net/ax25 ffff8c80b5ed6c00 ax0 TM6BVP-1 FE6BVP-1 1 0 0 0 13 50 0 3 0 300 0 0 4 10 5 2 256 0 0 18495 ffff8c80b5ed6400 ax0 TM6BVP-1 F6BVP-1 1 0 0 0 13 50 0 3 0 300 0 0 4 10 5 2 256 0 0 18493 ffff8c80b5ef5800 ax0 F6BVP-6 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18299 ffff8c80b5ef6000 ax0 TM6BVP-1 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18296 ffff8c80b5ed7400 ax0 TM6BVP-1 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18472 ffff8c80b5ed5800 ax0 F6BVP-7 F4BWT-9 1 0 0 0 18446744073709550 60 0 3 0 300 0 0 5 10 5 2 256 * * * ffff8c80b5ed5400 ax0 F6BVP-7 WA3MEZ-9 1 0 0 0 18446744073709550 60 0 3 0 300 0 0 5 10 5 2 256 * * * [root@f6bvp-6 bernard]# cat /proc/net/ax25 ffff8c80b5ed6c00 ax0 TM6BVP-1 FE6BVP-1 1 0 0 0 75 100 0 3 0 300 0 0 9 10 5 2 256 0 0 18495 ffff8c80b5ed6400 ax0 TM6BVP-1 F6BVP-1 1 0 0 0 75 100 0 3 0 300 0 0 9 10 5 2 256 0 0 18493 ffff8c80b5ef5800 ax0 F6BVP-6 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18299 ffff8c80b5ef6000 ax0 TM6BVP-1 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18296 ffff8c80b5ed7400 ax0 TM6BVP-1 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18472 ffff8c80b5ed5800 ax0 F6BVP-7 F4BWT-9 1 0 0 0 18446744073709549 100 0 3 0 300 0 0 9 10 5 2 256 * * * ffff8c80b5ed5400 ax0 F6BVP-7 WA3MEZ-9 1 0 0 0 18446744073709549 100 0 3 0 300 0 0 9 10 5 2 256 * * * [root@f6bvp-6 bernard]# cat /proc/net/ax25 ffff8c809025a800 ax0 TM6BVP-1 FE6BVP-1 1 0 0 0 25 60 0 3 0 300 0 0 5 10 5 2 256 0 0 29417 ffff8c809025bc00 ax0 TM6BVP-1 F6BVP-1 1 0 0 0 25 60 0 3 0 300 0 0 5 10 5 2 256 0 0 29416 ffff8c80b5ef5800 ax0 F6BVP-6 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18299 ffff8c80b5ef6000 ax0 TM6BVP-1 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18296 ffff8c80b5ed7400 ax0 TM6BVP-1 * 0 0 0 0 0 10 0 3 0 300 0 0 0 10 5 2 256 0 0 18472 ffff8c80b5ed5800 ax0 F6BVP-7 F4BWT-9 0 0 0 0 0 110 0 3 0 300 0 0 10 10 5 2 256 * * * ffff8c80b5ed5400 ax0 F6BVP-7 WA3MEZ-9 0 0 0 0 0 110 0 3 0 300 0 0 10 10 5 2 256 * * * While AX.25 connections are attempted with adjacent nodes (4th field =1) when system is started-up, one can see that 8th field of /proc/net/ax25 first two lines is counting down from 15 to 13 in above samples. At the same time, for example on line "ax0 F6BVP-7 WA3MEZ-9 1 0 0 0 1 60 0 3 0 300" the 8th field goes down from some number to 0, F6BVP-7 WA3MEZ-9 1 0 0 0 0 60 0 3 0 300 0 then it displays a very large number for a while, ax0 F6BVP-7 F4BWT-9 1 0 0 0 18446744073709549 100 0 3 0 300 0 then it starts again with a "normal" number. After a while, all unconnected entries stay stable : ax0 F6BVP-7 F4BWT-9 0 0 0 0 0 110 0 3 0 300 0 0 10 10 5 2 256 * * * And /proc/net/ax25 display the same unconnected entries forever. I also observed that this situation prevents a new connection to occur for the same destination call. I tried to apply some AX.25 patch I had received previously without success on stable kernel 4.1.38, and kernels 4.9.11 and 4.10.0. Same symptoms are seen on all my computers : i686 and RPis. I think this means that AX.25 sockets are never closed (destroyed) when a timer is expired after a connection attempt or a disconnection. Bernard, f6bvp
