From: syzbot <syzbot+c99d17aa44dbdba16ad2@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: [PATCH 1/1] add lock to wait queue
Date: Wed, 08 Apr 2026 05:20:10 -0700 [thread overview]
Message-ID: <69d647fa.050a0220.adfb3.0001.GAE@google.com> (raw)
In-Reply-To: <689daf88.050a0220.2d37a5.0001.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [PATCH 1/1] add lock to wait queue
Author: jakovnovak30@gmail.com
#syz test
---
drivers/net/wireless/marvell/libertas/firmware.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/marvell/libertas/firmware.c b/drivers/net/wireless/marvell/libertas/firmware.c
index f124110944b7..c01180f45500 100644
--- a/drivers/net/wireless/marvell/libertas/firmware.c
+++ b/drivers/net/wireless/marvell/libertas/firmware.c
@@ -113,7 +113,9 @@ static void load_next_firmware_from_table(struct lbs_private *priv)
void lbs_wait_for_firmware_load(struct lbs_private *priv)
{
- wait_event(priv->fw_waitq, priv->fw_callback == NULL);
+ spin_lock_irqsave(&priv->driver_lock, flags);
+ wait_event_lock_irq(priv->fw_waitq, priv->fw_callback == NULL, &priv->driver_lock);
+ spin_unlock_irqrestore(&priv->driver_lock, flags);
}
/**
--
2.53.0
next prev parent reply other threads:[~2026-04-08 12:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 9:42 [syzbot] [libertas?] INFO: task hung in lbs_remove_card syzbot
2026-02-27 11:22 ` syzbot
2026-02-28 3:35 ` Hillf Danton
2026-02-28 5:14 ` syzbot
2026-04-08 11:46 ` Forwarded: [PATCH 1/1] assert that the firmware has not been loaded before waiting for load completion syzbot
2026-04-08 12:11 ` Forwarded: [PATCH 1/1] add lock to wait queue syzbot
2026-04-08 12:20 ` syzbot [this message]
2026-04-08 13:10 ` syzbot
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=69d647fa.050a0220.adfb3.0001.GAE@google.com \
--to=syzbot+c99d17aa44dbdba16ad2@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.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