Bluetooth: Fix using a NULL inquiry cache entry
authorRam Malovany <ramm@ti.com>
Thu, 19 Jul 2012 07:26:10 +0000 (10:26 +0300)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 14 Sep 2012 17:00:18 +0000 (10:00 -0700)
commita8b8ad6dcf49c84c7a8633082191c6fd7539c355
tree04b83d3d6fd2d6c2c5fefff150b835d7a315bead
parenta431bd57a95921188f61096e5ce29d1b769be118
Bluetooth: Fix using a NULL inquiry cache entry

commit 7cc8380eb10347016d95bf6f9d842c2ae6d12932 upstream.

If the device was not found in a list of found devices names of which
are pending.This may happen in a case when HCI Remote Name Request
was sent as a part of incoming connection establishment procedure.
Hence there is no need to continue resolving a next name as it will
be done upon receiving another Remote Name Request Complete Event.
This will fix a kernel crash when trying to use this entry to resolve
the next name.

Signed-off-by: Ram Malovany <ramm@ti.com>
Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
net/bluetooth/hci_event.c