Hi Gustavo,
On Sat, 2011-07-02 at 21:49 -0400, Gustavo F. Padovan wrote:
> * Marcel Holtmann <marcel@xxxxxxxxxxxx> [2011-07-02 15:11:51 -0700]:
>
> > Hi Peter,
> >
> > > 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.
> > >
> > > Track as a device stat instead of logging.
> > >
> > > Signed-off-by: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>
> > > ---
> > > include/net/bluetooth/hci.h | 1 +
> > > net/bluetooth/l2cap_core.c | 8 ++++++++
> > > 2 files changed, 9 insertions(+), 0 deletions(-)
> > >
> > > 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 {
> > >
> > > /* ---- HCI Ioctl requests structures ---- */
> > > struct hci_dev_stats {
> > > + __u32 null_rx; /* # NULL pkts recvd */
> > > __u32 err_rx;
> > > __u32 err_tx;
> > > __u32 cmd_tx;
> >
> > you can not do it like this. This will break userspace API/ABI.
>
> Actually I don't see a point to have null_rx counter, just drop the packet 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
--
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
