From: Yves-Alexis Perez <corsac@corsac.net>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ming Lei <ming.lei@canonical.com>,
Johannes Berg <johannes@sipsolutions.net>,
Jouni Malinen <j@w1.fi>, Kees Cook <keescook@chromium.org>,
Jiri Kosina <jkosina@suse.cz>, Jiri Slaby <jslaby@suse.com>,
Tom Gundersen <teg@jklm.no>, Kay Sievers <kay@vrfy.org>,
Josh Boyer <jwboyer@fedoraproject.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andy Lutomirski <luto@amacapital.net>,
Harald Hoyer <harald@redhat.com>,
Seth Forshee <seth.forshee@canonical.com>,
Daniel Wagner <wagi@monom.org>, "4.2+" <stable@vger.kernel.org>
Subject: Re: [PATCH] firmware: fix async/manual firmware loading
Date: Thu, 10 Nov 2016 22:04:33 +0100 [thread overview]
Message-ID: <1478811873.31531.4.camel@corsac.net> (raw)
In-Reply-To: <CAB=NE6UNZLDhEFURvY_zP61WYNJU6CtpB+6FGXCvMGLvSfTd2w@mail.gmail.com>
On Thu, 2016-11-10 at 11:48 -0800, Luis R. Rodriguez wrote:
> > I haven't verified that this particular use case actually worked before,
> > but this code works with lower timeout values (e.g. 60 in the fallback
> > case), so this looks isolated.
>
> This is true, but as I noted the broken aspect was when the timeout
> was set to the max value.
>
> > The bug was clearly introduced in v4.0 by:
> >
> > 68ff2a00dbf5 "firmware_loader: handle timeout via
> > wait_for_completion_interruptible_timeout()"
> >
> > So please add a Fixes: and
> >
> > Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
>
> This I agree with, thanks for that, and because of this then:
>
> Acked-by: Luis R. Rodriguez <mcgrof@kernel.org>
>
> And because of this do recommend it for stable. I would still prefer
> at least a new re-submit with the respected tags and a changed commit
> log describing the reason for the fix, how the cast is an issue
> exactly, and how this is a regression.
Hi all,
I'm still slightly confused, but I can certainly re-submit it. I've added the
CC: stable because I first experienced it on a stable box, but indeed it was
during coding a kernel driver so it might not be what's expected in
“regression” here.
I'll try to collect the tag and rewrite the commit log, then re-submit,
hopefully not messing with git send-email this time.
Regards,
--
Yves-Alexis
next prev parent reply other threads:[~2016-11-10 21:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 14:50 Yves-Alexis Perez
2016-10-30 14:50 ` Yves-Alexis Perez
2016-10-30 17:28 ` Yves-Alexis Perez
2016-11-09 20:36 ` Luis R. Rodriguez
2016-11-09 22:02 ` Luis R. Rodriguez
2016-11-10 6:57 ` Yves-Alexis Perez
2016-11-09 20:39 ` Luis R. Rodriguez
2016-11-10 15:55 ` Greg Kroah-Hartman
2016-11-10 16:07 ` Luis R. Rodriguez
2016-11-10 18:52 ` Bjorn Andersson
2016-11-10 19:48 ` Luis R. Rodriguez
2016-11-10 21:04 ` Yves-Alexis Perez [this message]
2016-11-10 21:22 ` Luis R. Rodriguez
2016-11-10 19:18 ` Greg Kroah-Hartman
2016-11-10 19:49 ` Luis R. Rodriguez
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=1478811873.31531.4.camel@corsac.net \
--to=corsac@corsac.net \
--cc=bjorn.andersson@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=harald@redhat.com \
--cc=j@w1.fi \
--cc=jkosina@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=jslaby@suse.com \
--cc=jwboyer@fedoraproject.org \
--cc=kay@vrfy.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@kernel.org \
--cc=ming.lei@canonical.com \
--cc=seth.forshee@canonical.com \
--cc=stable@vger.kernel.org \
--cc=teg@jklm.no \
--cc=wagi@monom.org \
/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®