[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161110155511.GA10806@kroah.com>
Date: Thu, 10 Nov 2016 16:55:11 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "Luis R. Rodriguez" <mcgrof@...nel.org>
Cc: Yves-Alexis Perez <corsac@...sac.net>,
linux-kernel@...r.kernel.org,
Yves-Alexis Perez <corsac@...ian.org>,
Ming Lei <ming.lei@...onical.com>,
Johannes Berg <johannes@...solutions.net>,
Jouni Malinen <j@...fi>, Kees Cook <keescook@...omium.org>,
Jiri Kosina <jkosina@...e.cz>, Jiri Slaby <jslaby@...e.com>,
Tom Gundersen <teg@...m.no>, Kay Sievers <kay@...y.org>,
Josh Boyer <jwboyer@...oraproject.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Andy Lutomirski <luto@...capital.net>,
Harald Hoyer <harald@...hat.com>,
Seth Forshee <seth.forshee@...onical.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Daniel Wagner <wagi@...om.org>, stable@...r.kernel.org
Subject: Re: [PATCH] firmware: fix async/manual firmware loading
On Wed, Nov 09, 2016 at 09:39:21PM +0100, Luis R. Rodriguez wrote:
> On Sun, Oct 30, 2016 at 03:50:48PM +0100, Yves-Alexis Perez wrote:
> > From: Yves-Alexis Perez <corsac@...ian.org>
> >
> > wait_for_completion_interruptible_timeout() return value is either
> > -ERESTARTSYS (in case it was interrupted), 0 (in case the timeout expired)
> > or the number of jiffies left until timeout. The return value is stored in
> > a long, but in _request_firmware_load() it's silently casted to an int,
> > which can overflow and give a negative value, indicating an error.
> >
> > Fix this by re-using the timeout variable and only set retval when it's
> > safe.
>
> Please amend the commit log as I noted in the previous response, and
> resend.
>
> > Signed-off-by: Yves-Alexis Perez <corsac@...sac.net>
> > Cc: Ming Lei <ming.lei@...onical.com>
> > Cc: "Luis R. Rodriguez" <mcgrof@...nel.org>
> > Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>
> Other than the commit log you can add on you resend:
>
> Acked-by: Luis R. Rodriguez.
>
> Modulo I don't personally thing this this is sable material but I'll let
> Greg decide.
Does it fix a regression? A reported issue with an older kernel version
that people have hit? It shouldn't be hard to figure out if a patch
should be in stable or not...
thanks,
greg k-h
Powered by blists - more mailing lists