From: Sasha Levin <sasha.levin@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: Sasha Levin <sasha.levin@oracle.com>,
Ming Lei <ming.lei@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH] firmware class: remove from pending list on load failure
Date: Mon, 5 Jan 2015 10:41:21 -0500 [thread overview]
Message-ID: <1420472494-25836-1-git-send-email-sasha.levin@oracle.com> (raw)
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);
+ }
+
device_remove_file(f_dev, &dev_attr_loading);
err_del_bin_attr:
device_remove_bin_file(f_dev, &firmware_attr_data);
--
2.1.0
next reply other threads:[~2015-01-05 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 15:41 Sasha Levin [this message]
2015-01-07 4:52 ` [PATCH] firmware class: remove from pending list on load failure Ming Lei
2015-01-07 16:39 ` Sasha Levin
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=1420472494-25836-1-git-send-email-sasha.levin@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).