From: Johan Hedberg <johan.hedberg@intel.com>
Date: Tue, 1 Jul 2014 09:07:23 +0000 (+0300)
Subject: Bluetooth: Allow L2CAP getpeername() for BT_CONFIG state
X-Git-Tag: omap-for-v3.17/fixes-against-rc2~149^2~73^2~87^2~131
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bf19d51b768ceeccab12f932cac73b60b1d20bab;p=pandora-kernel.git

Bluetooth: Allow L2CAP getpeername() for BT_CONFIG state

We have all the necessary remote information for getpeername() when we
are in the BT_CONFIG state so this should be allowed. This is
particularly important for LE sockets where changing the security level
will temporarily move the socket into BT_CONFIG state.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
---

Reading git-diff-tree failed