From: Johan Hedberg <johan.hedberg@gmail.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH hcidump] Fix L2CAP cid matching
Date: Mon, 22 Aug 2011 11:04:07 +0300 [thread overview]
Message-ID: <20110822080407.GA11306@dell> (raw)
In-Reply-To: <1313254386.2254.8.camel@THOR>
Hi Peter,
On Sat, Aug 13, 2011, Peter Hurley wrote:
> If multiple ACL connections are using identical cid values, the L2CAP
> parser will match the first avail cid found in the cid table. This
> error often leads to incorrect psm determination, and thus incorrect
> parsing of higher-layer frames.
>
> When searching the cid table, a matching cid value must match by
> ACL handle as well.
> ---
> parser/l2cap.c | 42 +++++++++++++++++++++++-------------------
> 1 files changed, 23 insertions(+), 19 deletions(-)
Applied, but again I got this because of an unclean patch:
/home/jh/src/bluez-hcidump/.git/rebase-apply/patch:14: trailing whitespace.
static uint16_t get_psm(int in, uint16_t handle, uint16_t cid)
/home/jh/src/bluez-hcidump/.git/rebase-apply/patch:21: trailing whitespace.
if (table[i].handle == handle && table[i].cid == cid)
/home/jh/src/bluez-hcidump/.git/rebase-apply/patch:27: trailing whitespace.
static uint16_t get_num(int in, uint16_t handle, uint16_t cid)
/home/jh/src/bluez-hcidump/.git/rebase-apply/patch:34: trailing whitespace.
if (table[i].handle == handle && table[i].cid == cid)
/home/jh/src/bluez-hcidump/.git/rebase-apply/patch:40: trailing whitespace.
static void set_mode(int in, uint16_t handle, uint16_t cid, uint8_t mode)
warning: squelched 18 whitespace errors
warning: 23 lines add whitespace errors.
Johan
prev parent reply other threads:[~2011-08-22 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 16:53 [PATCH hcidump] Fix L2CAP cid matching Peter Hurley
2011-08-22 8:04 ` Johan Hedberg [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=20110822080407.GA11306@dell \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=peter@hurleysoftware.com \
/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).