From: Peter Hurley <peter@hurleysoftware.com>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] Bluetooth: l2cap: fix NULL ACL packet handling
Date: Tue, 5 Jul 2011 11:13:41 -0400 [thread overview]
Message-ID: <1309878821.4125.23.camel@THOR> (raw)
In-Reply-To: <20110703014958.GA2706@joana>
Hi Gustavo,
On Sat, 2011-07-02 at 21:49 -0400, Gustavo F. Padovan wrote:
> * Marcel Holtmann <marcel@holtmann.org> [2011-07-02 15:11:51 -0700]:
>=20
> > Hi Peter,
> >=20
> > > A 0-length ACL continuation-fragment is a valid NULL packet. Remote
> > > devices can use the FLOW indicator in the ACL packet header to
> > > flow-control ACL packets without sending a payload.
> > >=20
> > > Track as a device stat instead of logging.
> > >=20
> > > Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
> > > ---
> > > include/net/bluetooth/hci.h | 1 +
> > > net/bluetooth/l2cap_core.c | 8 ++++++++
> > > 2 files changed, 9 insertions(+), 0 deletions(-)
> > >=20
> > > diff --git a/include/net/bluetooth/hci.h b/include/net/bluetooth/hci.=
h
> > > index 0c20227..de7ed81 100644
> > > --- a/include/net/bluetooth/hci.h
> > > +++ b/include/net/bluetooth/hci.h
> > > @@ -1142,6 +1142,7 @@ struct hci_ufilter {
> > > =20
> > > /* ---- HCI Ioctl requests structures ---- */
> > > struct hci_dev_stats {
> > > + __u32 null_rx; /* # NULL pkts recvd */
> > > __u32 err_rx;
> > > __u32 err_tx;
> > > __u32 cmd_tx;
> >=20
> > you can not do it like this. This will break userspace API/ABI.
>=20
> Actually I don't see a point to have null_rx counter, just drop the packe=
t and
> we are done.
Although a null_rx counter doesn't really qualify as critical or even
necessary, I thought it might be useful in helping users troubleshoot
apparent link quality issues - especially those relating to A2DP, like
dropouts and sputter.
Currently, some users experience significant audio quality issues that I
suspect is actually *not* related to link quality nor old LMP
implementations. Often these are accompanied by logs full of "Unexpected
continuation frame ..." messages. By 'full', I mean on the order of
30,000 messages in < 10 minutes.
Although I thought it appropriate to not log an error message for an
accepted flow control method, it seems a shame to simply ignore it.
Regards,
Peter
next prev parent reply other threads:[~2011-07-05 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 17:44 [PATCH v2 1/1] Bluetooth: l2cap: fix NULL ACL packet handling Peter Hurley
2011-07-02 22:11 ` Marcel Holtmann
2011-07-03 1:49 ` Gustavo F. Padovan
2011-07-05 15:13 ` Peter Hurley [this message]
2011-07-05 14:55 ` Peter Hurley
2011-07-05 16:35 ` Marcel Holtmann
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=1309878821.4125.23.camel@THOR \
--to=peter@hurleysoftware.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=padovan@profusion.mobi \
/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).