linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] firmware class: remove from pending list on load failure
Date: Wed, 07 Jan 2015 11:39:36 -0500	[thread overview]
Message-ID: <54AD6148.6030703@oracle.com> (raw)
In-Reply-To: <CACVXFVPUF1x8YDwHtYzoC6LiPy22Lr2bZC-N73+NakFMBrEUFw@mail.gmail.com>

On 01/06/2015 11:52 PM, Ming Lei wrote:
> On Mon, Jan 5, 2015 at 11:41 PM, Sasha Levin <sasha.levin@oracle.com> wrote:
>> > If we failed loading the firmware we have to make sure it leaves the pending
>> > list if abort wasn't executed for it.
>> >
>> > Otherwise we'd free an object still on the pending list and corrupt it.
>> >
>> > Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
>> > ---
>> >  drivers/base/firmware_class.c | 11 ++++++++++-
>> >  1 file changed, 10 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
>> > index 58470c3..8ccf6cf4 100644
>> > --- a/drivers/base/firmware_class.c
>> > +++ b/drivers/base/firmware_class.c
>> > @@ -929,9 +929,18 @@ static int _request_firmware_load(struct firmware_priv *fw_priv,
>> >         cancel_delayed_work_sync(&fw_priv->timeout_work);
>> >         if (is_fw_load_aborted(buf))
>> >                 retval = -EAGAIN;
>> > -       else if (!buf->data)
>> > +       else if (!buf->data) {
>> >                 retval = -ENOMEM;
>> >
>> > +               /*
>> > +                * We failed loading, but abort was never done so we
>> > +                * need to remove it from the pending list ourselves.
>> > +                */
>> > +               mutex_lock(&fw_lock);
>> > +               list_del_init(&buf->pending_list);
>> > +               mutex_unlock(&fw_lock);
> The buf is always removed before the complete_all(), isn't it? Or did
> you observe the issue?

Not in the case where userspacehelper fails. Yes, this is not a theoretical
thing and can be easily reproduced.


Thanks,
Sasha

  reply	other threads:[~2015-01-07 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 15:41 [PATCH] firmware class: remove from pending list on load failure Sasha Levin
2015-01-07  4:52 ` Ming Lei
2015-01-07 16:39   ` Sasha Levin [this message]
2015-01-08  2:15     ` Ming Lei
2015-01-08  2:37       ` Sasha Levin
2015-01-08  3:06         ` Ming Lei
2015-01-08  4:36           ` Ming Lei

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=54AD6148.6030703@oracle.com \
    --to=sasha.levin@oracle.com \
    --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;
as well as URLs for NNTP newsgroup(s).