mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
	Ming Lei <ming.lei@canonical.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] firmware: Prevent oops on delayed abort
Date: Wed, 4 Jan 2017 17:50:46 +0100	[thread overview]
Message-ID: <20170104165046.GH13946@wotan.suse.de> (raw)
In-Reply-To: <20170104154749.GI9639@nuc-i3427.alporthouse.com>

On Wed, Jan 04, 2017 at 03:47:49PM +0000, Chris Wilson wrote:
> On Wed, Jan 04, 2017 at 04:40:49PM +0100, Luis R. Rodriguez wrote:
> > On Wed, Jan 04, 2017 at 07:12:11PM +0800, Ming Lei wrote:
> > > On Wed, Jan 4, 2017 at 5:31 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > > > If the firmware load is slow and cancelled, we may call fw_load_abort()
> > > > twice and promptly oops on the second with a NULL dereference.
> > > >
> > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > > Cc: Ming Lei <ming.lei@canonical.com>
> > > > Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>
> > > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > ---
> > > >  drivers/base/firmware_class.c | 3 +++
> > > >  1 file changed, 3 insertions(+)
> > > >
> > > > diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
> > > > index 4497d263209f..d03e21c1d2f3 100644
> > > > --- a/drivers/base/firmware_class.c
> > > > +++ b/drivers/base/firmware_class.c
> > > > @@ -557,6 +557,9 @@ static void fw_load_abort(struct firmware_priv *fw_priv)
> > > >  {
> > > >         struct firmware_buf *buf = fw_priv->buf;
> > > >
> > > > +       if (!buf)
> > > > +               return;
> > > > +
> > > >         __fw_load_abort(buf);
> > > >
> > > >         /* avoid user action after loading abort */
> > > > --
> > > > 2.11.0
> > > >
> > > 
> > > Looks fine,
> > > 
> > > Acked-by: Ming Lei <ming.lei@canonical.com>
> > 
> > But does this fix an actual oops or just theoretical? If it does can you
> > include the trace, and amend the commit log to Cc stable so this gets
> > properly propagated into the stable kernels?
> 
> Actual oops, I was going to include the oops from dmesg but that was
> lost on a the forced reboot. It's fairly clear the cause once you read
> the callers.

I see, if you can reproduce and include it that would be greatly appreciated,
and please re-submit and Cc stable on the commit log, if you can indicate
as of what kernel this is needed even better (Fixes: tag might help).

  Luis

      reply	other threads:[~2017-01-04 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  9:31 Chris Wilson
2017-01-04 11:12 ` Ming Lei
2017-01-04 15:40   ` Luis R. Rodriguez
2017-01-04 15:47     ` Chris Wilson
2017-01-04 16:50       ` Luis R. Rodriguez [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=20170104165046.GH13946@wotan.suse.de \
    --to=mcgrof@kernel.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.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®