From: Dan Carpenter <dan.carpenter@oracle.com>
To: yoshfuji@linux-ipv6.org
Cc: linux1394-devel@lists.sourceforge.net, netdev@vger.kernel.org,
kbuild@01.org
Subject: re: firewire net, ipv4 arp: Extend hardware address and remove driver-level packet inspection.
Date: Tue, 2 Apr 2013 09:36:41 +0300 [thread overview]
Message-ID: <20130402063641.GB4826@longonot.mountain> (raw)
Hello YOSHIFUJI Hideaki / 吉藤英明,
The patch 6752c8db8e0c: "firewire net, ipv4 arp: Extend hardware
address and remove driver-level packet inspection." from Mar 25,
2013, leads to the following warning:
"drivers/firewire/net.c:278 fwnet_header_parse()
error: memcpy() 'haddr' too small (8 vs 16)"
drivers/firewire/net.c
276 static int fwnet_header_parse(const struct sk_buff *skb, unsigned char *haddr)
277 {
278 memcpy(haddr, skb->dev->dev_addr, FWNET_ALEN);
^^^^^^^^^^
We bumped this to 16 bytes and made the fwnet_header and fwnet_hwaddr
structs bigger. But according to Smatch this is still an 8 byte buffer
here. Either phw.hw_addr or sll->sll_addr.
The call tree would be:
-> packet_rcv()
-> dev_parse_header()
-> fwnet_header_parse()
279
280 return FWNET_ALEN;
281 }
282
regards,
dan carpenter
reply other threads:[~2013-04-02 6:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130402063641.GB4826@longonot.mountain \
--to=dan.carpenter@oracle.com \
--cc=kbuild@01.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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