From: Marcel Holtmann <marcel@holtmann.org>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] Bluetooth: l2cap: fix NULL ACL packet handling
Date: Tue, 05 Jul 2011 18:35:59 +0200 [thread overview]
Message-ID: <1309883760.21109.30.camel@aeonflux> (raw)
In-Reply-To: <1309877745.4125.7.camel@THOR>
Hi Peter,
> > > /* ---- 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.
>
> Thanks for the definitive answer, Marcel.
>
> I suspected as much (which is why I noted in the accompanying cover that
> this would be incompatible with previous userspace versions of this
> ioctl).
>
> Is the general plan then to freeze the existing raw HCI interface and
> only implement new userspace <-> kernel interfaces on mgmtops?
we can extend the existing ioctl, but only in an API/ABI compatible
fashion. So adding the null_rx at the end of the struct might work. And
we might wanna add null_rx + null_tx to be consistent.
The problem part here is that the stats struct is also nested in the
info struct. We might get lucky here since it is nested at the end.
Regards
Marcel
prev parent reply other threads:[~2011-07-05 16:35 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
2011-07-05 14:55 ` Peter Hurley
2011-07-05 16:35 ` Marcel Holtmann [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=1309883760.21109.30.camel@aeonflux \
--to=marcel@holtmann.org \
--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).