From: syzbot <syzbot+92c6dd14aaa230be6855@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [PATCH wireless] wifi: ath6kl: remove WARN on bad firmware input
Date: Tue, 17 Jun 2025 02:45:43 -0700 [thread overview]
Message-ID: <68513947.a70a0220.395abc.0210.GAE@google.com> (raw)
In-Reply-To: <00000000000096ee8f061e991433@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: [PATCH wireless] wifi: ath6kl: remove WARN on bad firmware input
Author: johannes@sipsolutions.net
From: Johannes Berg <johannes.berg@intel.com>
If the firmware gives bad input, that's nothing to do with
the driver's stack at this point etc., so the WARN_ON()
doesn't add any value. Additionally, this is one of the
top syzbot reports now. Just print a message, and as an
added bonus, print the sizes too.
Reported-by: syzbot+92c6dd14aaa230be6855@syzkaller.appspotmail.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
---
#syz test
---
drivers/net/wireless/ath/ath6kl/bmi.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath6kl/bmi.c b/drivers/net/wireless/ath/ath6kl/bmi.c
index af98e871199d..5a9e93fd1ef4 100644
--- a/drivers/net/wireless/ath/ath6kl/bmi.c
+++ b/drivers/net/wireless/ath/ath6kl/bmi.c
@@ -87,7 +87,9 @@ int ath6kl_bmi_get_target_info(struct ath6kl *ar,
* We need to do some backwards compatibility to make this work.
*/
if (le32_to_cpu(targ_info->byte_count) != sizeof(*targ_info)) {
- WARN_ON(1);
+ ath6kl_err("mismatched byte count %d vs. expected %zd\n",
+ le32_to_cpu(targ_info->byte_count),
+ sizeof(*targ_info));
return -EINVAL;
}
--
2.49.0
prev parent reply other threads:[~2025-06-17 9:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 6:11 [syzbot] [wireless?] [usb?] WARNING in ath6kl_bmi_get_target_info (2) syzbot
2024-08-25 4:29 ` Edward Adam Davis
2024-08-25 4:57 ` syzbot
2024-08-25 7:10 ` [PATCH] wifi: ath6kl: Check that the read operation returns a data length of 0 Edward Adam Davis
2024-08-25 7:25 ` Greg KH
2024-08-25 8:14 ` Edward Adam Davis
2024-08-25 8:34 ` Greg KH
2024-08-25 10:09 ` Edward Adam Davis
2024-08-25 11:25 ` Greg KH
2024-08-25 14:03 ` Edward Adam Davis
2024-08-25 14:21 ` [PATCH V2] wifi: ath6kl: Replace ath6kl_usb_submit_ctrl_in with usb_control_msg_recv Edward Adam Davis
2024-08-25 14:50 ` Sergei Shtylyov
2024-08-25 15:07 ` Sergei Shtylyov
2024-08-26 5:04 ` Greg KH
2024-08-26 11:12 ` Edward Adam Davis
2024-08-26 11:19 ` [PATCH V3] " Edward Adam Davis
2024-08-26 11:25 ` Greg KH
2024-08-26 11:26 ` Greg KH
2024-08-26 12:29 ` [PATCH V4 1/2] " Edward Adam Davis
2024-08-26 13:12 ` Greg KH
2024-08-26 13:12 ` Greg KH
[not found] ` <20240826122955.2674569-3-eadavis@qq.com>
2024-08-26 12:29 ` [PATCH V4 2/2] wifi: ath6kl: remove ath6kl_usb_submit_ctrl_in Edward Adam Davis
2024-08-26 13:13 ` Greg KH
2024-08-26 13:44 ` [PATCH V5 1/2] wifi: ath6kl: Replace ath6kl_usb_submit_ctrl_in with usb_control_msg_recv Edward Adam Davis
[not found] ` <20240826134418.2744882-3-eadavis@qq.com>
2024-08-26 13:44 ` [PATCH V5 2/2] wifi: ath6kl: remove ath6kl_usb_submit_ctrl_in Edward Adam Davis
2024-08-26 13:01 ` [PATCH V4 1/2] wifi: ath6kl: Replace ath6kl_usb_submit_ctrl_in with usb_control_msg_recv Edward Adam Davis
[not found] ` <20240826130154.2706792-3-eadavis@qq.com>
2024-08-26 13:01 ` [PATCH V4 2/2] wifi: ath6kl: remove ath6kl_usb_submit_ctrl_in Edward Adam Davis
2024-08-26 11:42 ` [PATCH V2] wifi: ath6kl: Replace ath6kl_usb_submit_ctrl_in with usb_control_msg_recv Kalle Valo
2024-08-26 13:06 ` Edward Adam Davis
2024-08-26 15:01 ` Kalle Valo
2024-08-26 22:51 ` [PATCH V6 1/2] " Edward Adam Davis
[not found] ` <20240826225107.2817092-3-eadavis@qq.com>
2024-08-26 22:51 ` [PATCH V6 2/2] wifi: ath6kl: remove ath6kl_usb_submit_ctrl_in Edward Adam Davis
2025-06-17 9:45 ` syzbot [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=68513947.a70a0220.395abc.0210.GAE@google.com \
--to=syzbot+92c6dd14aaa230be6855@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