From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8188eu: Replace a custom function with crc32_le()
Date: Tue, 13 Jul 2021 19:52:45 +0200 [thread overview]
Message-ID: <3537977.lmtE3BSfzd@localhost.localdomain> (raw)
In-Reply-To: <YO2MJ97grAbMQ1ms@kroah.com>
On Tuesday, July 13, 2021 2:50:47 PM CEST Greg Kroah-Hartman wrote:
> On Thu, Jul 01, 2021 at 03:38:09PM +0200, Fabio M. De Francesco wrote:
> > Use crc32_le in place of the custom getcrc32. This change makes GCC
> > to warn about incorrect castings to the restricted type __le32, but
> > they can be safely ignored because crc32_le calculates bitwise
> > little-endian Ethernet AUTODIN II CRC32.
> >
> > Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> > ---
> >
> > drivers/staging/rtl8188eu/core/rtw_security.c | 22 ++++---------------
> > 1 file changed, 4 insertions(+), 18 deletions(-)
> >
> > diff --git a/drivers/staging/rtl8188eu/core/rtw_security.c
> > b/drivers/staging/rtl8188eu/core/rtw_security.c index
1b2cb6196463..5f010cb66970
> > 100644
> > --- a/drivers/staging/rtl8188eu/core/rtw_security.c
> > +++ b/drivers/staging/rtl8188eu/core/rtw_security.c
> > @@ -111,21 +111,6 @@ static void crc32_init(void)
> >
[...]
>
> Why are you casting a native endian return value to a little endian
> pointer?
>
Actually, I was not sure whether or not crc32_le() returns native or little
endian values:
(1) That "_le" in crc32_le() made me think it calculates little endian values
and the documentation of the function is a little misleading where it affirms
that "[crc32_le()] calculates *bitwise
little-endian* Ethernet AUTODIN II CRC32".
(2) Furthermore, I took commit b97fad10de387 as a model for my patch. You
applied that commit and it makes exactly the same change that I make in my
patch. I still cannot understand why you took that. Maybe I'm missing
something that I can't still see. What is it?
>
> Are you _SURE_ that is correct?
>
To summarize, I thought that crc32_le is some way returning an LE value in an
array of four u8 (aka an unsigned integer).
Now I suppose I have to change "*((__le32 *)crc) = ~crc32_le(~0, payload,
length);" to "*((__le32 *)crc) = cpu_to_le32(~crc32_le(~0, payload, length)".
Thanks,
Fabio
> We can not just ignore warnings, they are there for a reason. Or if
> not, then fix the code up to not have the warnings, but I can't take
> this as-is, sorry.
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2021-07-13 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 13:38 [PATCH] staging: rtl8188eu: Replace a custom function with crc32_le() Fabio M. De Francesco
2021-07-01 14:52 ` David Laight
2021-07-01 15:23 ` Fabio M. De Francesco
2021-07-01 15:54 ` David Laight
2021-07-01 16:10 ` Fabio M. De Francesco
2021-07-10 0:25 ` kernel test robot
2021-07-10 14:38 ` Fabio M. De Francesco
2021-07-10 20:42 ` David Laight
2021-07-13 12:50 ` Greg Kroah-Hartman
2021-07-13 17:52 ` Fabio M. De Francesco [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=3537977.lmtE3BSfzd@localhost.localdomain \
--to=fmdefrancesco@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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