From: Hauke Mehrtens <hauke@hauke-m.de>
To: Joe Perches <joe@perches.com>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
"Rafał Miłecki" <zajec5@gmail.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ssb: fix unaligned access to mac address
Date: Wed, 20 Feb 2013 20:17:06 +0100 [thread overview]
Message-ID: <51252132.3050603@hauke-m.de> (raw)
In-Reply-To: <1361384969.2219.4.camel@joe-AO722>
On 02/20/2013 07:29 PM, Joe Perches wrote:
> On Wed, 2013-02-20 at 11:56 -0600, Larry Finger wrote:
>> On 02/20/2013 11:31 AM, Joe Perches wrote:
>>> On Mon, 2013-02-18 at 17:09 +0100, Rafał Miłecki wrote:
>>>> 2013/2/16 Hauke Mehrtens <hauke@hauke-m.de>:
>>>>> The mac address should be aligned to u16 to prevent an unaligned access
>>>>> in drivers/ssb/pci.c where it is casted to __be16.
>>> []
>>>>> diff --git a/include/linux/ssb/ssb.h b/include/linux/ssb/ssb.h
>>> []
>>>>> @@ -26,6 +26,7 @@ struct ssb_sprom_core_pwr_info {
>>>>>
>>>>> struct ssb_sprom {
>>>>> u8 revision;
>>>>> + u8 country_code; /* Country Code */
>>>>> u8 il0mac[6]; /* MAC address for 802.11b/g */
>>>>
>>>> It looks a little hacky to me too, it's easy to forget about that
>>>> requirement and break that again in the future.
>>>>
>>>> What about not casting il0mac to u16 at all? Maybe we should just fill
>>>> it as u8 (which it is)?
>>>>
>>>
>>> Perhaps this?
>>>
>>> From: Joe Perches <joe@perches.com>
>>> Subject: [PATCH] ssb: pci: Standardize a function to get mac address
>>>
>>> Don't require alignment of mac addresses to u16.
...
>> I like the looks of sprom_get_mac() over that ugly *(((__be16 *)out->il0mac)
>> construct, but this patch breaks ssb. The resulting MAC address is all ones. I
>> have not yet figured out the problem.
>
> Dunno, I must have done something stupid.
>
> I don't have one of these but the transform
> looked correct when I did it.
>
> I'm not sure it's the best solution anyway
> because some of the other ether address
> functions like compare_ether_addr also
> require 2 byte alignment and cast to u16.
Your patch looks good (haven't tested it), but as you said we should
still align the mac addresses to u16 so functions like
compare_ether_addr work with them.
There is also a v2 of my patch:
http://www.spinics.net/lists/linux-wireless/msg103628.html
Hauke
next prev parent reply other threads:[~2013-02-20 19:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 13:25 [PATCH] ssb: fix unaligned access to mac address Hauke Mehrtens
2013-02-18 10:10 ` Johannes Berg
2013-02-18 16:09 ` Rafał Miłecki
2013-02-20 17:31 ` Joe Perches
2013-02-20 17:56 ` Larry Finger
2013-02-20 18:29 ` Joe Perches
2013-02-20 19:17 ` Hauke Mehrtens [this message]
2013-02-20 20:11 ` Joe Perches
2013-02-21 3:34 ` Larry Finger
2013-03-09 23:02 ` Rafał Miłecki
2013-03-09 23:31 ` Larry Finger
2013-03-09 23:56 ` Larry Finger
2013-03-10 11:36 ` Rafał Miłecki
2013-03-10 17:35 ` Larry Finger
2013-03-10 20:57 ` Rafał Miłecki
2013-02-20 20:16 ` [PATCH 2/2] ssb: Convert ssb_printk to ssb_<level> Joe Perches
2013-02-20 19:07 ` [PATCH] ssb: fix unaligned access to mac address Joe Perches
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=51252132.3050603@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=Larry.Finger@lwfinger.net \
--cc=joe@perches.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=zajec5@gmail.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).