From: syzbot <syzbot+b05dabaed0b1f0b0a5e4@syzkaller.appspotmail.com>
To: ath9k-devel@qca.qualcomm.com, davem@davemloft.net,
edumazet@google.com, gregkh@linuxfoundation.org,
john.ogness@linutronix.de, kuba@kernel.org, kvalo@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, pmladek@suse.com, rostedt@goodmis.org,
senozhatsky@chromium.org, syzkaller-bugs@googlegroups.com,
toke@toke.dk
Subject: Re: [syzbot] KASAN: use-after-free Read in ath9k_hif_usb_reg_in_cb (3)
Date: Fri, 17 Jun 2022 03:22:08 -0700 [thread overview]
Message-ID: <00000000000066643305e1a22061@google.com> (raw)
In-Reply-To: <00000000000006b92e05d6ee4fce@google.com>
syzbot suspects this issue was fixed by commit:
commit 09c5ba0aa2fcfdadb17d045c3ee6f86d69270df7
Author: John Ogness <john.ogness@linutronix.de>
Date: Thu Apr 21 21:22:48 2022 +0000
printk: add kthread console printers
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10e88490080000
start commit: 210e04ff7681 Merge tag 'pci-v5.18-fixes-1' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=902c5209311d387c
dashboard link: https://syzkaller.appspot.com/bug?extid=b05dabaed0b1f0b0a5e4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f2c009f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11b20b35f00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: printk: add kthread console printers
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-06-17 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 5:38 [syzbot] KASAN: use-after-free Read in ath9k_hif_usb_reg_in_cb (3) syzbot
2022-02-15 6:57 ` syzbot
2022-06-17 10:22 ` 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=00000000000066643305e1a22061@google.com \
--to=syzbot+b05dabaed0b1f0b0a5e4@syzkaller.appspotmail.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=syzkaller-bugs@googlegroups.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).