From: Kalle Valo <kvalo@kernel.org>
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: ath9k-devel@qca.qualcomm.com, davem@davemloft.net,
kuba@kernel.org, linville@tuxdriver.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+f83a1df1ed4f67e8d8ad@syzkaller.appspotmail.com,
"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: [PATCH] ath9k_htc: fix uninit value bugs
Date: Thu, 03 Feb 2022 10:39:12 +0200 [thread overview]
Message-ID: <87bkzocpjj.fsf@kernel.org> (raw)
In-Reply-To: <0647fd91-f0a7-4cf7-4f80-cd5dc3f2f6a2@gmail.com> (Pavel Skripkin's message of "Fri, 28 Jan 2022 23:52:42 +0300")
Pavel Skripkin <paskripkin@gmail.com> writes:
> Hi Kalle,
>
> On 1/28/22 15:32, Kalle Valo wrote:
>>> Fixes: fb9987d0f748 ("ath9k_htc: Support for AR9271 chipset.")
>>> Reported-by: syzbot+f83a1df1ed4f67e8d8ad@syzkaller.appspotmail.com
>>> Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
>>> Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
>>
>> Patch applied to ath-next branch of ath.git, thanks.
>>
>> d1e0df1c57bd ath9k_htc: fix uninit value bugs
>>
>
> Thanks, Kalle! Can you also, please, check out this one too :)
> Quite old, but syzbot is getting mad with this bug (like 20k hits). Thanks!
>
>
> https://lore.kernel.org/all/20210922164204.32680-1-paskripkin@gmail.com/
I already provided feedback on August 6th:
"Separate patch for cleanups, please."
https://patchwork.kernel.org/project/linux-wireless/patch/20210804194841.14544-1-paskripkin@gmail.com/
Please submit v2. And Toke is the new ath9k maintainer, so please CC him
as well.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2022-02-03 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 12:27 [PATCH] ath9k_htc: fix uninit value bugs Pavel Skripkin
2022-01-17 12:57 ` Kalle Valo
2022-01-17 18:35 ` Pavel Skripkin
2022-01-28 12:32 ` Kalle Valo
2022-01-28 20:52 ` Pavel Skripkin
2022-02-03 8:39 ` Kalle Valo [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=87bkzocpjj.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=paskripkin@gmail.com \
--cc=syzbot+f83a1df1ed4f67e8d8ad@syzkaller.appspotmail.com \
--cc=toke@toke.dk \
/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).