Bluetooth: L2CAP: Fix not initializing sk_peer_pid
authorLuiz Augusto von Dentz <luiz.von.dentz@intel.com>
Thu, 7 Oct 2021 20:26:25 +0000 (13:26 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 27 Jan 2022 10:03:01 +0000 (11:03 +0100)
commit6c1ad4aeeab4d04b538efddeb84c5b51919526bb
tree602ed2881e7f7f422a529c66197f313d8c3fd350
parent0da09030aae4a3c9de4699e7ce71085639f8c378
Bluetooth: L2CAP: Fix not initializing sk_peer_pid

[ Upstream commit f5ff291098f70a70b344df1e388596755c3c8315 ]

In order to group sockets being connected using L2CAP_MODE_EXT_FLOWCTL
the pid is used but sk_peer_pid was not being initialized as it is
currently only done for af_unix.

Fixes: b48596d1dc25 ("Bluetooth: L2CAP: Add get_peer_pid callback")
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
net/bluetooth/l2cap_sock.c