From: Gustavo Padovan <padovan@profusion.mobi>
To: ilia.kolominsky@gmail.com
Cc: linux-bluetooth@vger.kernel.org, Ilia Kolomisnky <iliak@ti.com>
Subject: Re: [PATCH] Bluetooth-next: Fixes l2cap "command reject" reply according to spec.
Date: Wed, 6 Jul 2011 11:43:01 -0300 [thread overview]
Message-ID: <20110706144301.GA7786@joana> (raw)
In-Reply-To: <1309676174-20157-1-git-send-email-iliak@ti.com>
Hi Ilia,
I may have missed this patch, sorry.
* ilia.kolominsky@gmail.com <ilia.kolominsky@gmail.com> [2011-07-03 09:56:14 +0300]:
> From: Ilia Kolomisnky <iliak@ti.com>
>
> There can 3 reasons for the "command reject" reply produced
> by the stack. Each such reply should be accompanied by the
> relevand data ( as defined in spec. ). Currently there is one
> instance of "command reject" reply with reason "invalid cid"
> wich is fixed. Also, added clean-up definitions related to the
> "command reject" replies.
>
> Signed-off-by: Ilia Kolomisnky <iliak@ti.com>
> ---
> include/net/bluetooth/l2cap.h | 19 ++++++++++++++++++-
> net/bluetooth/l2cap_core.c | 15 +++++++++------
> 2 files changed, 27 insertions(+), 7 deletions(-)
>
> diff --git a/include/net/bluetooth/l2cap.h b/include/net/bluetooth/l2cap.h
> index 9c18e55..6dee791 100644
> --- a/include/net/bluetooth/l2cap.h
> +++ b/include/net/bluetooth/l2cap.h
> @@ -130,6 +130,12 @@ struct l2cap_conninfo {
> #define L2CAP_SDU_END 0x8000
> #define L2CAP_SDU_CONTINUE 0xC000
>
> +/* L2CAP Command rej. reasons */
> +#define L2CAP_CMD_NOT_UNDERSTOOD 0x0000
> +#define L2CAP_CMD_MTU_EXCEEDED 0x0001
s/CMD/REJ
> +#define L2CAP_CMD_INV_CID 0x0002
#define L2CAP_REJ_INVALID_CID
> +
> +
> /* L2CAP structures */
> struct l2cap_hdr {
> __le16 len;
> @@ -144,8 +150,19 @@ struct l2cap_cmd_hdr {
> } __packed;
> #define L2CAP_CMD_HDR_SIZE 4
>
> -struct l2cap_cmd_rej {
> +struct l2cap_cmd_rej_unk {
> + __le16 reason;
> +} __packed;
> +
> +struct l2cap_cmd_rej_mtu {
> + __le16 reason;
> + __le16 max_mtu;
> +} __packed;
> +
> +struct l2cap_cmd_rej_cid {
> __le16 reason;
> + __le16 loc_cid;
> + __le16 rem_cid;
call theses scid and dcid.
Gustavo
prev parent reply other threads:[~2011-07-06 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 6:56 [PATCH] Bluetooth-next: Fixes l2cap "command reject" reply according to spec ilia.kolominsky
2011-07-06 7:13 ` Ilia, Kolominsky
2011-07-06 14:43 ` Gustavo Padovan [this message]
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=20110706144301.GA7786@joana \
--to=padovan@profusion.mobi \
--cc=ilia.kolominsky@gmail.com \
--cc=iliak@ti.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