From: syzbot <syzbot+381102a7292a374fe8a7@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [wireless?] [usb?] WARNING in __carl9170_tx_process_status
Date: Mon, 06 Jul 2026 10:48:09 -0700 [thread overview]
Message-ID: <6a4bea59.57639fcc.86d58.0002.GAE@google.com> (raw)
In-Reply-To: <6a489e31.b42ede87.8bd1.0009.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [wireless?] [usb?] WARNING in __carl9170_tx_process_status
Author: malayarout91@gmail.com
Hi,
Please test the following patch.
#syz test
diff --git a/drivers/net/wireless/ath/carl9170/tx.c
b/drivers/net/wireless/ath/carl9170/tx.c
index 59caf1e4b158..b5a028abe4c6 100644
--- a/drivers/net/wireless/ath/carl9170/tx.c
+++ b/drivers/net/wireless/ath/carl9170/tx.c
@@ -514,8 +514,9 @@ static struct sk_buff
*carl9170_get_queued_skb(struct ar9170 *ar, u8 cookie,
struct sk_buff_head *queue)
{
struct sk_buff *skb;
+ unsigned long flags;
- spin_lock_bh(&queue->lock);
+ spin_lock_irqsave(&queue->lock, flags);
skb_queue_walk(queue, skb) {
struct _carl9170_tx_superframe *txc = (void *) skb->data;
@@ -523,12 +524,12 @@ static struct sk_buff
*carl9170_get_queued_skb(struct ar9170 *ar, u8 cookie,
continue;
__skb_unlink(skb, queue);
- spin_unlock_bh(&queue->lock);
+ spin_unlock_irqrestore(&queue->lock, flags);
carl9170_release_dev_space(ar, skb);
return skb;
}
- spin_unlock_bh(&queue->lock);
+ spin_unlock_irqrestore(&queue->lock, flags);
return NULL;
}
next prev parent reply other threads:[~2026-07-06 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 5:46 [syzbot] [wireless?] [usb?] WARNING in __carl9170_tx_process_status syzbot
2026-07-06 17:48 ` syzbot [this message]
2026-07-06 18:16 ` Forwarded: " 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=6a4bea59.57639fcc.86d58.0002.GAE@google.com \
--to=syzbot+381102a7292a374fe8a7@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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