Re: [RFC] Bluetooth: Lock l2cap chan in sockopt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Andrei -

On Wed, 6 Jun 2012, Andrei Emeltchenko wrote:

From: Andrei Emeltchenko <andrei.emeltchenko@xxxxxxxxx>


Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@xxxxxxxxx>

Commit message is quite short :)  (I know, it's just an RFC)

---
net/bluetooth/l2cap_sock.c |   12 ++++++++++++
1 file changed, 12 insertions(+)

diff --git a/net/bluetooth/l2cap_sock.c b/net/bluetooth/l2cap_sock.c
index a4bb27e..373ce9c 100644
--- a/net/bluetooth/l2cap_sock.c
+++ b/net/bluetooth/l2cap_sock.c
@@ -275,6 +275,7 @@ static int l2cap_sock_getsockopt_old(struct socket *sock, int optname, char __us
	if (get_user(len, optlen))
		return -EFAULT;

+	l2cap_chan_lock(chan);
	lock_sock(sk);

	switch (optname) {
@@ -345,6 +346,8 @@ static int l2cap_sock_getsockopt_old(struct socket *sock, int optname, char __us
	}

	release_sock(sk);
+	l2cap_chan_unlock(chan);
+
	return err;
}

@@ -367,6 +370,7 @@ static int l2cap_sock_getsockopt(struct socket *sock, int level, int optname, ch
	if (get_user(len, optlen))
		return -EFAULT;

+	l2cap_chan_lock(chan);
	lock_sock(sk);

	switch (optname) {
@@ -442,6 +446,8 @@ static int l2cap_sock_getsockopt(struct socket *sock, int level, int optname, ch
	}

	release_sock(sk);
+	l2cap_chan_unlock(chan);
+
	return err;
}

@@ -471,6 +477,7 @@ static int l2cap_sock_setsockopt_old(struct socket *sock, int optname, char __us

	BT_DBG("sk %p", sk);

+	l2cap_chan_lock(chan);
	lock_sock(sk);

	switch (optname) {
@@ -556,6 +563,8 @@ static int l2cap_sock_setsockopt_old(struct socket *sock, int optname, char __us
	}

	release_sock(sk);
+	l2cap_chan_unlock(chan);
+
	return err;
}

@@ -577,6 +586,7 @@ static int l2cap_sock_setsockopt(struct socket *sock, int level, int optname, ch
	if (level != SOL_BLUETOOTH)
		return -ENOPROTOOPT;

+	l2cap_chan_lock(chan);
	lock_sock(sk);

	switch (optname) {
@@ -729,6 +739,8 @@ static int l2cap_sock_setsockopt(struct socket *sock, int level, int optname, ch
	}

	release_sock(sk);
+	l2cap_chan_unlock(chan);
+
	return err;
}

--
1.7.9.5

Code looks good to me. In the near future, BT_CHANNEL_POLICY will call in to the L2CAP core to do channel moves, but I think it helps to already have the lock held in that case.


--
Mat Martineau
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
--
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


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux