linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Skripkin <paskripkin@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath9k-devel@qca.qualcomm.com, davem@davemloft.net,
	kuba@kernel.org, Sujith.Manoharan@atheros.com,
	linville@tuxdriver.com, vasanth@atheros.com,
	senthilkumar@atheros.com, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzbot+03110230a11411024147@syzkaller.appspotmail.com,
	syzbot+c6dde1f690b60e0b9fbe@syzkaller.appspotmail.com
Subject: Re: [PATCH RESEND] net: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb
Date: Sat, 2 Oct 2021 16:14:43 +0300	[thread overview]
Message-ID: <215bf5da-d69d-a764-62e8-6b6e0702d5db@gmail.com> (raw)
In-Reply-To: <87pmsnh8qx.fsf@codeaurora.org>

On 10/2/21 16:11, Kalle Valo wrote:
>> Hi, ath9k maintainers!
>>
>> Does this patch need any further work? I can't see any comments on it
>> since 8/6/21 and I can't see it on wireless patchwork.
>>
>> If this bug is already fixed and I've overlooked a fix commit, please,
>> let me know. As I see syzbot hits this bug really often [1]
> 
> See my other mail I just sent about ath9k syzbot patches:
> 
> https://lore.kernel.org/linux-wireless/87tuhzhdyq.fsf@codeaurora.org/
> 
> In summary: please wait patiently once I'm able to test the syzbot
> patches on a real device.
> 

I see, thank you clarifying the situation. I understand, that 
maintaining ath9k devices alone is not easy task

Thanks again


With regards,
Pavel Skripkin

  reply	other threads:[~2021-10-02 13:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 19:48 [PATCH] net: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb Pavel Skripkin
2021-08-04 19:57 ` Pavel Skripkin
2021-08-31 10:43   ` Pavel Skripkin
2021-09-19 17:28     ` Pavel Skripkin
2021-09-22 16:42       ` [PATCH RESEND] " Pavel Skripkin
2021-10-02 13:05         ` Pavel Skripkin
2021-10-02 13:11           ` Kalle Valo
2021-10-02 13:14             ` Pavel Skripkin [this message]
2021-08-06  9:06 ` [PATCH] " Kalle Valo
2021-08-13 15:01 ` Pavel Skripkin

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=215bf5da-d69d-a764-62e8-6b6e0702d5db@gmail.com \
    --to=paskripkin@gmail.com \
    --cc=Sujith.Manoharan@atheros.com \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=senthilkumar@atheros.com \
    --cc=syzbot+03110230a11411024147@syzkaller.appspotmail.com \
    --cc=syzbot+c6dde1f690b60e0b9fbe@syzkaller.appspotmail.com \
    --cc=vasanth@atheros.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).