Do the ax25_list_lock, ax25_dev_lock, linkfail_lockreally, ax25_frag_lock and listen_lock have to be bh-safe? Do the netrom and rose locks have to be bh-safe? A device might be deleted after lookup in the SIOCADDRT ioctl but before it's being used. Routes to a device being taken down might be deleted by ax25_rt_device_down but added by somebody else before the device has been deleted fully. The ax25_rt_find_route synopsys is pervert but I somehow had to deal with the race caused by the static variable in it's previous implementation. Implement proper socket locking in netrom and rose. Check socket locking when ax25_rcv is sending to raw sockets. In particular ax25_send_to_raw() seems fishy. Heck - ax25_rcv is fishy. Handle XID and TEST frames properly. 'cgit logo'/> index : net-next.git
net-next plumbingsTobias Klauser
summaryrefslogtreecommitdiff
path: root/net/tipc
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2017-01-30 16:38:39 -0500
committerDavid S. Miller <davem@davemloft.net>2017-01-30 16:38:39 -0500
commit0d29ed28da63dd893395c343c7e78b078de93ceb (patch)
treebd8c1e88f2ed53a20dfe9a502d878716da861675 /net/tipc
parent2b89ed65a6f201a6a4f0450ad289aa4bf491608c (diff)
parenta06393ed03167771246c4c43192d9c264bc48412 (diff)
Merge tag 'linux-can-fixes-for-4.10-20170130' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can
Marc Kleine-Budde says: ==================== pull-request: can 2017-01-30 this is a pull request of one patch. The patch is by Oliver Hartkopp and fixes the hrtimer/tasklet termination in bcm op removal. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/tipc')