summaryrefslogtreecommitdiff
path: root/net/bluetooth/hci_debugfs.c
diff options
context:
space:
mode:
authorSimon Wunderlich <simon@open-mesh.com>2015-06-24 15:50:19 +0300
committerAntonio Quartulli <antonio@meshcoding.com>2015-08-05 01:31:47 +0300
commit27a4d5efd417b6ef3190e9af357715532d4617a3 (patch)
treef5ca6408c633f58c211a2b1e3b1e2b9347470382 /net/bluetooth/hci_debugfs.c
parentef72706a0543d0c3a5ab29bd6378fdfb368118d9 (diff)
downloadlinux-27a4d5efd417b6ef3190e9af357715532d4617a3.tar.xz
batman-adv: initialize up/down values when adding a gateway
Without this initialization, gateways which actually announce up/down bandwidth of 0/0 could be added. If these nodes get purged via _batadv_purge_orig() later, the gw_node structure does not get removed since batadv_gw_node_delete() updates the gw_node with up/down bandwidth of 0/0, and the updating function then discards the change and does not free gw_node. This results in leaking the gw_node structures, which references other structures: gw_node -> orig_node -> orig_node_ifinfo -> hardif. When removing the interface later, the open reference on the hardif may cause hangs with the infamous "unregister_netdevice: waiting for mesh1 to become free. Usage count = 1" message. Signed-off-by: Simon Wunderlich <simon@open-mesh.com> Signed-off-by: Marek Lindner <mareklindner@neomailbox.ch> Signed-off-by: Antonio Quartulli <antonio@meshcoding.com>
Diffstat (limited to 'net/bluetooth/hci_debugfs.c')
0 files changed, 0 insertions, 0 deletions