From: yann.poupet@free.fr
To: linux-kernel@vger.kernel.org
Subject: [PROBLEM]: potential unaligned memory access in drivers/usb/gadget/rndis.c
Date: Wed, 11 Mar 2009 13:51:08 +0100 (CET) [thread overview]
Message-ID: <3848726.1723791236775868071.JavaMail.root@spooler2-g27.priv.proxad.net> (raw)
Hello,
while working on a 2.6.18.2 kernel on ARM9 arch., I noticed RNDIS module might trigger lots of unaligned access exceptions.
Looks like it comes from rndis_add_hdr() function, which uses pointer from skb_pull as if it is aligned on a 4bytes boundary.
void rndis_add_hdr (struct sk_buff *skb)
{
struct rndis_packet_msg_type *header;
if (!skb)
return;
header = (void *) skb_push (skb, sizeof *header);
memset (header, 0, sizeof *header);
header->MessageType = __constant_cpu_to_le32(REMOTE_NDIS_PACKET_MSG);
header->MessageLength = cpu_to_le32(skb->len);
header->DataOffset = __constant_cpu_to_le32 (36);
header->DataLength = cpu_to_le32(skb->len - sizeof *header);
}
It happened to me that skb_pull() returns a pointer to a location not aligned on a 4 bytes boundary.
As a quick workaround, I modified the code to:
void rndis_add_hdr (struct sk_buff *skb)
{
struct rndis_packet_msg_type *header;
static struct rndis_packet_msg_type new = {
__constant_cpu_to_le32(REMOTE_NDIS_PACKET_MSG), /* MessageType */
0, /* MessageLength */
__constant_cpu_to_le32 (36), /* DataOffset */
0, /* DataLength */
0, /* OOBDataOffset */
0, /* OOBDataLength */
0, /* NumOOBDataElements */
0, /* PerPacketInfoOffset */
0, /* PerPacketInfoLength */
0, /* VcHandle */
0, /* Reserved */
};
if (!skb)
return;
header = (void *) skb_push (skb, sizeof *header);
memset (header, 0, sizeof *header); /* probably not necessary */
new.MessageLength = cpu_to_le32(skb->len);
new.DataLength = cpu_to_le32(skb->len - sizeof *header);
memcpy((u8*)header,(u8*)&new,sizeof(new));
}
and did not have the unaligned exceptions anymore.
I had a look at rndis.c in latest kernel version (2.6.28.7), the rndis_add_hdr() function is the same as for 2.6.18.2.
Hope this helps.
Regards,
Yann Poupet.
next reply other threads:[~2009-03-11 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 12:51 yann.poupet [this message]
2009-03-12 6:51 ` [PROBLEM]: potential unaligned memory access in drivers/usb/gadget/rndis.c Andrew Morton
2009-03-12 23:51 ` Harvey Harrison
2009-03-13 20:52 ` David Miller
2009-03-16 8:38 ` David Brownell
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=3848726.1723791236775868071.JavaMail.root@spooler2-g27.priv.proxad.net \
--to=yann.poupet@free.fr \
--cc=linux-kernel@vger.kernel.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