From: Alexander Aring <alex.aring@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-wpan@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH bluetooth-next] af_ieee802154: make header uapi conform
Date: Sat, 3 Jan 2015 12:02:32 +0100 [thread overview]
Message-ID: <20150103110229.GA10722@omega> (raw)
In-Reply-To: <715AC34D-9929-4959-A0E9-48B748F8E22F@holtmann.org>
Hi Marcel,
On Fri, Jan 02, 2015 at 05:02:57PM -0800, Marcel Holtmann wrote:
> Hi Alex,
>
> > This patch uses __u16 and __u8 instead of u16 and u8 typedefs. These
> > typedefs coming from linux/types.h and are also easily available in
> > standard userspace environments. The af_ieee802154 header is normally
> > an userspace header. For now, we just copy this header in an userspace
> > application.
> >
> > Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> > ---
> > The "int addr_type" should be the above enum. I will fix this later. This
> > header has also other various issues. For now I just want the same version
> > in userspace which is also inside kernelspace.
> >
> > include/net/af_ieee802154.h | 7 ++++---
> > 1 file changed, 4 insertions(+), 3 deletions(-)
> >
> > diff --git a/include/net/af_ieee802154.h b/include/net/af_ieee802154.h
> > index 7d38e2f..63af3f2 100644
> > --- a/include/net/af_ieee802154.h
> > +++ b/include/net/af_ieee802154.h
> > @@ -21,6 +21,7 @@
> > #define _AF_IEEE802154_H
> >
> > #include <linux/socket.h> /* for sa_family_t */
> > +#include <linux/types.h>
> >
> > enum {
> > IEEE802154_ADDR_NONE = 0x0,
> > @@ -34,10 +35,10 @@ enum {
> >
> > struct ieee802154_addr_sa {
> > int addr_type;
> > - u16 pan_id;
> > + __u16 pan_id;
> > union {
> > - u8 hwaddr[IEEE802154_ADDR_LEN];
> > - u16 short_addr;
> > + __u8 hwaddr[IEEE802154_ADDR_LEN];
> > + __u16 short_addr;
> > };
> > };
>
> which address information is this? Are these the socket addresses you use for bind(), connect() etc.
>
> In that case shouldn't this be sa_family_t instead.
>
I making some research related to this and I think there no good news.
First to your question:
The af_ieee802154.h contains an another struct, the "sockaddr_ieee802154":
struct sockaddr_ieee802154 {
sa_family_t family; /* AF_IEEE802154 */
struct ieee802154_addr_sa addr;
};
See [0]. I think that is what you mean.
This is struct is for bind(), connect(). I have a small userspace
application which based on the old userspace tools "izchat".
This struct will be a cast to "struct sockaddr":
struct sockaddr {
sa_family_t sa_family; /* address family, AF_xxx */
char sa_data[14]; /* 14 bytes of protocol address */
};
See [1].
This will imply that sizeof(struct sockaddr_ieee802154) MUST NOT above
the 14 bytes sa_data. (Which is for the protocol address information)
IMPORTANT NOTE: There is no BUILD_BUG_ON to check on this!
I calculate it on 32 bit machines it's:
int (4) + u16 (2) + hwaddr (8) = 14 bytes
Okay that fits, but on 64 bit machines:
int (8) + u16 (2) + hwaddr (8) = 18 bytes
Okay, I don't know if we have a bufferoverflow now here. Maybe the last
4 bytes are simply cutted and this socket interface simple doesn't work
on 64 bit machines in some cases. If we have a bufferoverflow we should
fix it in stable otherwise maybe just fixing that it works on 64 bit
machines.
I didn't work much with the socket interface, I want more 6LoWPAN
support, the socket interface for 802.15.4 is more for running closed
standards inside userspace to avoid license issues and I suppose the
socket interface code needs a complete rework.
Do you have some suggestion how to fix that? Maybe just make "int
addr_type" to u8? I am fine with that, simple forget the enum because we
have only few bytes for socket address data.
- Alex
[0] http://lxr.free-electrons.com/source/include/net/af_ieee802154.h#L52
[1] http://lxr.free-electrons.com/source/include/linux/socket.h#L29
prev parent reply other threads:[~2015-01-03 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 15:44 [PATCH bluetooth-next] af_ieee802154: make header uapi conform Alexander Aring
2015-01-03 1:02 ` Marcel Holtmann
2015-01-03 11:02 ` Alexander Aring [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=20150103110229.GA10722@omega \
--to=alex.aring@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.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