Hi Johan, > We're interested in whether an authentication request is because of a > remote or local action. So far hci_conn_security() has been used both > for incoming and outgoing actions (e.g. RFCOMM or L2CAP connect > requests) so without some modifications it cannot know which peer is > responsible for requesting authentication. > > This patch adds a new "bool initiator" parameter to hci_conn_security() > to indicate which side is responsible for the request and updates the > current users to pass this information correspondingly. > > Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> > --- > include/net/bluetooth/hci_core.h | 3 ++- > include/net/bluetooth/l2cap.h | 2 +- > net/bluetooth/hci_conn.c | 3 ++- > net/bluetooth/l2cap_core.c | 15 ++++++++------- > net/bluetooth/l2cap_sock.c | 2 +- > net/bluetooth/mgmt.c | 2 +- > net/bluetooth/rfcomm/core.c | 3 ++- > 7 files changed, 17 insertions(+), 13 deletions(-) patch has been applied to bluetooth-next tree. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
