From: Dan Carpenter <dan.carpenter@oracle.com>
To: Thibaut Robert <thibaut.robert@gmail.com>
Cc: Aditya Shankar <aditya.shankar@microchip.com>,
Ganesh Krishna <ganesh.krishna@microchip.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: wilc1000: fix some endianness sparse warnings
Date: Tue, 5 Jun 2018 10:36:31 +0300 [thread overview]
Message-ID: <20180605073631.cvp2iuef4yb636jz@mwanda> (raw)
In-Reply-To: <20180604193250.GB32753@L80496>
On Mon, Jun 04, 2018 at 09:32:50PM +0200, Thibaut Robert wrote:
> Le mercredi 30 mai 2018 à 14:17:25 (+0300), Dan Carpenter a écrit :
> > On Tue, May 29, 2018 at 09:11:43PM +0200, Thibaut Robert wrote:
> > > diff --git a/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c b/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
> > > index e248702ee519..745bf5ca2622 100644
> > > --- a/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
> > > +++ b/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
> > > @@ -1431,7 +1431,7 @@ void wilc_wfi_p2p_rx(struct net_device *dev, u8 *buff, u32 size)
> > >
> > > freq = ieee80211_channel_to_frequency(curr_channel, NL80211_BAND_2GHZ);
> > >
> > > - if (!ieee80211_is_action(buff[FRAME_TYPE_ID])) {
> > > + if (!ieee80211_is_action(cpu_to_le16(buff[FRAME_TYPE_ID]))) {
> >
> > "buff" comes from the network, it's going to be little endian, not cpu
> > endian. The rest of the function treats it as CPU endian but I'm pretty
> > sure it's wrong...
> buff comes from the network but we are looking at single byte here.
> ieee80211_is_action expects an le16, so we I added this to extend an u8
> to an le16. Is this incorrect ?
>
> Or maybe we the buff has the second byte ? but that I can't tell.
You raise a good point that I hadn't seen. The original code is clearly
buggy. But your fix isn't correct either... The other thing to
consider is that cpu_to_le16() is basically a cast to u16 on x86 so it's
a no-op here.
Really the right thing is to not treat buff as an array of u8 but a
struct. The code assumes that frame_type is 0-255 but probably it's
supposed to go up to U16_MAX.
struct whatever {
__le16 frame_type;
...
There probably is already a struct like that, but I don't know what it
is. I don't know this code at all, I'm just guessing.
regards,
dan carpenter
next prev parent reply other threads:[~2018-06-05 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 19:11 Thibaut Robert
2018-05-30 11:17 ` Dan Carpenter
2018-06-04 19:32 ` Thibaut Robert
2018-06-05 7:36 ` Dan Carpenter [this message]
2018-06-05 8:33 ` Thibaut Robert
2018-06-05 6:12 ` Ajay Singh
2018-06-05 8:53 ` Dan Carpenter
2018-05-30 14:50 ` Ajay Singh
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=20180605073631.cvp2iuef4yb636jz@mwanda \
--to=dan.carpenter@oracle.com \
--cc=aditya.shankar@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=thibaut.robert@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
all inboxes | Powered by JetHome®