From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: "Usyskin, Alexander" <alexander.usyskin@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [char-misc v4.4.y 2/2] mei: bus: type promotion bug in mei_nfc_if_version()
Date: Mon, 24 Sep 2018 12:53:07 +0200 [thread overview]
Message-ID: <20180924105307.GB16476@kroah.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B9D9B4CF9@hasmsx108.ger.corp.intel.com>
On Sun, Sep 23, 2018 at 05:49:02AM +0000, Winkler, Tomas wrote:
> >
> > On Tue, Sep 04, 2018 at 01:43:04AM +0300, Tomas Winkler wrote:
> > > From: Dan Carpenter <dan.carpenter@oracle.com>
> > >
> > > commit b40b3e9358fbafff6a4ba0f4b9658f6617146f9c upstream
> > >
> > > 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.
> > >
> > > Cc: <stable@vger.kernel.org> # 4.4
> >
> > I also need a version of this patch for 4.18.y, 4.14.y, and 4.9.y before I will
> > consider adding it to 4.4.y, as we do not want anyone to ever get a
> > regression moving to a new kernel.
>
> Right, I've started from the wrong end.
> Now I've posted the patches for the rest of the required long running versions.
Thanks for all of these, now queued up.
greg k-h
prev parent reply other threads:[~2018-09-24 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 22:43 [stable v4.4.y 1/2] mei: me: allow runtime pm for platform with D0i3 Tomas Winkler
2018-09-03 22:43 ` [char-misc v4.4.y 2/2] mei: bus: type promotion bug in mei_nfc_if_version() Tomas Winkler
2018-09-13 12:35 ` Greg Kroah-Hartman
2018-09-23 5:49 ` Winkler, Tomas
2018-09-24 10:53 ` Greg Kroah-Hartman [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=20180924105307.GB16476@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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
Powered by JetHome