Root/
1 | Do the ax25_list_lock, ax25_dev_lock, linkfail_lockreally, ax25_frag_lock and |
2 | listen_lock have to be bh-safe? |
3 | |
4 | Do the netrom and rose locks have to be bh-safe? |
5 | |
6 | A device might be deleted after lookup in the SIOCADDRT ioctl but before it's |
7 | being used. |
8 | |
9 | Routes to a device being taken down might be deleted by ax25_rt_device_down |
10 | but added by somebody else before the device has been deleted fully. |
11 | |
12 | The ax25_rt_find_route synopsys is pervert but I somehow had to deal with |
13 | the race caused by the static variable in it's previous implementation. |
14 | |
15 | Implement proper socket locking in netrom and rose. |
16 | |
17 | Check socket locking when ax25_rcv is sending to raw sockets. In particular |
18 | ax25_send_to_raw() seems fishy. Heck - ax25_rcv is fishy. |
19 | |
20 | Handle XID and TEST frames properly. |
21 |
Branches:
ben-wpan
ben-wpan-stefan
javiroman/ks7010
jz-2.6.34
jz-2.6.34-rc5
jz-2.6.34-rc6
jz-2.6.34-rc7
jz-2.6.35
jz-2.6.36
jz-2.6.37
jz-2.6.38
jz-2.6.39
jz-3.0
jz-3.1
jz-3.11
jz-3.12
jz-3.13
jz-3.15
jz-3.16
jz-3.18-dt
jz-3.2
jz-3.3
jz-3.4
jz-3.5
jz-3.6
jz-3.6-rc2-pwm
jz-3.9
jz-3.9-clk
jz-3.9-rc8
jz47xx
jz47xx-2.6.38
master
Tags:
od-2011-09-04
od-2011-09-18
v2.6.34-rc5
v2.6.34-rc6
v2.6.34-rc7
v3.9