aboutsummaryrefslogtreecommitdiffstats
path: root/net/ax25/TODO
diff options
context:
space:
mode:
Diffstat (limited to 'net/ax25/TODO')
-rw-r--r--net/ax25/TODO24
1 files changed, 24 insertions, 0 deletions
diff --git a/net/ax25/TODO b/net/ax25/TODO
new file mode 100644
index 000000000000..4089c49e45cc
--- /dev/null
+++ b/net/ax25/TODO
@@ -0,0 +1,24 @@
1Do the ax25_list_lock, ax25_dev_lock, linkfail_lockreally, ax25_frag_lock and
2listen_lock have to be bh-safe?
3
4Do the netrom and rose locks have to be bh-safe?
5
6A device might be deleted after lookup in the SIOCADDRT ioctl but before it's
7being used.
8
9Routes to a device being taken down might be deleted by ax25_rt_device_down
10but added by somebody else before the device has been deleted fully.
11
12Massive amounts of lock_kernel / unlock_kernel are just a temporary solution to
13get around the removal of SOCKOPS_WRAP. A serious locking strategy has to be
14implemented.
15
16The ax25_rt_find_route synopsys is pervert but I somehow had to deal with
17the race caused by the static variable in it's previous implementation.
18
19Implement proper socket locking in netrom and rose.
20
21Check socket locking when ax25_rcv is sending to raw sockets. In particular
22ax25_send_to_raw() seems fishy. Heck - ax25_rcv is fishy.
23
24Handle XID and TEST frames properly.