From: Julia Lawall <julia.lawall@lip6.fr>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
"Usyskin, Alexander" <alexander.usyskin@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>
Subject: RE: [PATCH] mei: bus: type promotion bug in mei_nfc_if_version()
Date: Wed, 4 Jul 2018 16:45:29 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1807041644450.4944@hadrien> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B9D95BCDE@hasmsx108.ger.corp.intel.com>
On Wed, 4 Jul 2018, Winkler, Tomas wrote:
>
> > On Wed, Jul 04, 2018 at 01:57:44PM +0000, Winkler, Tomas wrote:
> > > >
> > > > On Wed, Jul 04, 2018 at 01:59:14PM +0200, Julia Lawall wrote:
> > > > >
> > > > >
> > > > > On Wed, 4 Jul 2018, Dan Carpenter wrote:
> > > > >
> > > > > > We accidentally removed the check for negative returns without
> > > > > > considering the issue of type promotion. The "if_version_length"
> > > > > > variable is type size_t so if __mei_cl_recv() returns a negative
> > > > > > then "bytes_recv" is type promoted to a high positive value and
> > > > > > treated as success.
> > > > > >
> > > > > > Fixes: 582ab27a063a ("mei: bus: fix received data size check in
> > > > > > NFC
> > > > > > fixup")
> > > > > > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > > > > >
> > > > > > diff --git a/drivers/misc/mei/bus-fixup.c
> > > > > > b/drivers/misc/mei/bus-fixup.c index 0208c4b027c5..fa0236a5e59a
> > > > > > 100644
> > > > > > --- a/drivers/misc/mei/bus-fixup.c
> > > > > > +++ b/drivers/misc/mei/bus-fixup.c
> > > > > > @@ -267,7 +267,7 @@ static int mei_nfc_if_version(struct mei_cl
> > > > > > *cl,
> > > > > >
> > > > > > ret = 0;
> > > > > > bytes_recv = __mei_cl_recv(cl, (u8 *)reply, if_version_length,
> > 0);
> > > > > > - if (bytes_recv < if_version_length) {
> > > > > > + if (bytes_recv < 0 || bytes_recv < if_version_length) {
> > > > >
> > > > > Is this preferred to adding an int cast?
> > > >
> > > > I don't think it matters. I kind of like explicitly testing for
> > > > negative but maybe later people will just remove the check like we
> > > > did here? You could do it a bunch of different ways:
> > > >
> > > > 1: if (ret < 0 || ret < ARRAY_SIZE(xxx))
> > > > 2: if (ret < (int)ARRAY_SIZE(xxx))
> > > > 3: if (ret != ARRAY_SIZE(xxx))
> > > >
> > > > They're all equivalent. I guess I don't like casting too much. My
> > > > first approach to fixing this was just to declare if_version_length
> > > > as an int, but then I saw that originally there was a "bytes_recv < 0"
> > > > check and decided to go that way instead.
> > >
> > > Actually bytes_recv should be probably of ssize_t type, so could be the
> > if_version_length.
> > >
> > > How did you find this, I haven't seen it in reported by sparse, smatch and I
> > believe -Wsign-compare is suppressed in compilation warnings.
> >
> > It's a new thing. Julia noticed this kind of bug first
Actually, I got it from Joe Perches, for the sizeof case :)
julia
> > and I have been mucking
> > around with it in Smatch as well. My Smatch check has too many false
> > positives to publish right now because it thinks a some common functions
> > like ffs() return negative error codes.
>
> I guess this is why it is suppressed in the compilation warnings in the first place.
> Maybe need to disable it selectively, like for fss, just not sure how bad is that with false positive reports.
>
>
> Thanks
> Tomas
>
>
next prev parent reply other threads:[~2018-07-04 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 9:34 Dan Carpenter
2018-07-04 11:59 ` Julia Lawall
2018-07-04 12:16 ` Dan Carpenter
2018-07-04 13:57 ` Winkler, Tomas
2018-07-04 14:15 ` Dan Carpenter
2018-07-04 14:25 ` Winkler, Tomas
2018-07-04 14:45 ` Julia Lawall [this message]
2018-07-07 15:32 ` Greg Kroah-Hartman
2018-07-09 11:36 ` Winkler, Tomas
2018-07-09 12:03 ` Greg Kroah-Hartman
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=alpine.DEB.2.20.1807041644450.4944@hadrien \
--to=julia.lawall@lip6.fr \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.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®