From: johan.hedberg@gmail.com
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v3 2/8] Bluetooth: Fix L2CAP command reject reason
Date: Sat, 14 Sep 2013 20:28:25 +0300 [thread overview]
Message-ID: <1379179711-16436-3-git-send-email-johan.hedberg@gmail.com> (raw)
In-Reply-To: <1379179711-16436-1-git-send-email-johan.hedberg@gmail.com>
From: Johan Hedberg <johan.hedberg@intel.com>
There are several possible reason codes that can be sent in the command
reject L2CAP packet. Before this patch the code has used a hard-coded
single response code ("command not understood"). This patch adds a
helper function to map the return value of an L2CAP handler function to
the correct command reject reason.
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
---
net/bluetooth/l2cap_core.c | 22 ++++++++++++++++++----
1 file changed, 18 insertions(+), 4 deletions(-)
diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
index b3bb7bc..83acb28 100644
--- a/net/bluetooth/l2cap_core.c
+++ b/net/bluetooth/l2cap_core.c
@@ -5294,6 +5294,20 @@ static inline int l2cap_le_sig_cmd(struct l2cap_conn *conn,
}
}
+static u16 l2cap_err_to_reason(int err)
+{
+ switch (err) {
+ case -EFAULT:
+ return L2CAP_REJ_INVALID_CID;
+ case -EMSGSIZE:
+ return L2CAP_REJ_MTU_EXCEEDED;
+ case -EINVAL:
+ case -EPROTO:
+ default:
+ return L2CAP_REJ_NOT_UNDERSTOOD;
+ }
+}
+
static inline void l2cap_le_sig_channel(struct l2cap_conn *conn,
struct sk_buff *skb)
{
@@ -5323,11 +5337,11 @@ static inline void l2cap_le_sig_channel(struct l2cap_conn *conn,
err = l2cap_le_sig_cmd(conn, &cmd, data);
if (err) {
struct l2cap_cmd_rej_unk rej;
+ u16 reason = l2cap_err_to_reason(err);
BT_ERR("Wrong link type (%d)", err);
- /* FIXME: Map err to a valid reason */
- rej.reason = __constant_cpu_to_le16(L2CAP_REJ_NOT_UNDERSTOOD);
+ rej.reason = cpu_to_le16(reason);
l2cap_send_cmd(conn, cmd.ident, L2CAP_COMMAND_REJ,
sizeof(rej), &rej);
}
@@ -5368,11 +5382,11 @@ static inline void l2cap_sig_channel(struct l2cap_conn *conn,
err = l2cap_bredr_sig_cmd(conn, &cmd, cmd_len, data);
if (err) {
struct l2cap_cmd_rej_unk rej;
+ u16 reason = l2cap_err_to_reason(err);
BT_ERR("Wrong link type (%d)", err);
- /* FIXME: Map err to a valid reason */
- rej.reason = __constant_cpu_to_le16(L2CAP_REJ_NOT_UNDERSTOOD);
+ rej.reason = cpu_to_le16(reason);
l2cap_send_cmd(conn, cmd.ident, L2CAP_COMMAND_REJ,
sizeof(rej), &rej);
}
--
1.8.4.rc3
next prev parent reply other threads:[~2013-09-14 17:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 17:28 [PATCH v3 0/8] Bluetooth: Various L2CAP fixes johan.hedberg
2013-09-14 17:28 ` [PATCH v3 1/8] Bluetooth: Remove unused event mask struct johan.hedberg
2013-09-15 1:47 ` Marcel Holtmann
2013-09-14 17:28 ` johan.hedberg [this message]
2013-09-15 1:52 ` [PATCH v3 2/8] Bluetooth: Fix L2CAP command reject reason Marcel Holtmann
2013-09-15 6:34 ` Johan Hedberg
2013-09-15 16:05 ` Marcel Holtmann
2013-09-14 17:28 ` [PATCH v3 3/8] Bluetooth: Fix double error response for l2cap_create_chan_req johan.hedberg
2013-09-14 17:28 ` [PATCH v3 4/8] Bluetooth: Fix L2CAP Disconnect response for unknown CID johan.hedberg
2013-09-14 17:28 ` [PATCH v3 5/8] Bluetooth: Fix error code for invalid CID in l2cap_config_req johan.hedberg
2013-09-15 1:49 ` Marcel Holtmann
2013-09-15 6:30 ` Johan Hedberg
2013-09-15 16:03 ` Marcel Holtmann
2013-09-15 18:15 ` Johan Hedberg
2013-09-15 19:04 ` Marcel Holtmann
2013-09-15 20:00 ` Johan Hedberg
2013-09-16 0:17 ` Marcel Holtmann
2013-09-16 9:54 ` Johan Hedberg
2013-09-14 17:28 ` [PATCH v3 6/8] Bluetooth: Fix sending responses to identified L2CAP response packets johan.hedberg
2013-09-15 1:54 ` Marcel Holtmann
2013-09-14 17:28 ` [PATCH v3 7/8] Bluetooth: Fix responding to invalid L2CAP signaling commands johan.hedberg
2013-09-14 17:28 ` [PATCH v3 8/8] Bluetooth: Fix waiting for clearing of BT_SK_SUSPEND flag johan.hedberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1379179711-16436-3-git-send-email-johan.hedberg@gmail.com \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).