From: syzbot <syzbot+d625c772c7814faabef9@syzkaller.appspotmail.com>
To: andreyknvl@google.com, bxb5544@psu.edu, davem@davemloft.net,
edumazet@google.com, gregkh@linuxfoundation.org,
ingrassia@epigenesys.com, khoroshilov@ispras.ru, 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, pchelkin@ispras.ru,
quic_kvalo@quicinc.com, syzkaller-bugs@googlegroups.com,
toke@toke.dk
Subject: Re: [syzbot] WARNING in ath9k_hif_usb_alloc_urbs/usb_submit_urb
Date: Mon, 30 Jan 2023 08:04:18 -0800 [thread overview]
Message-ID: <0000000000001ca15605f37d5ec6@google.com> (raw)
In-Reply-To: <000000000000ba030f05a87330b6@google.com>
syzbot suspects this issue was fixed by commit:
commit 16ef02bad239f11f322df8425d302be62f0443ce
Author: Fedor Pchelkin <pchelkin@ispras.ru>
Date: Sat Oct 8 21:15:32 2022 +0000
wifi: ath9k: verify the expected usb_endpoints are present
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=153e9c11480000
start commit: 55be6084c8e0 Merge tag 'timers-core-2022-10-05' of git://g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=df75278aabf0681a
dashboard link: https://syzkaller.appspot.com/bug?extid=d625c772c7814faabef9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=138d8cc2880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12b2dc3c880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: wifi: ath9k: verify the expected usb_endpoints are present
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-01-30 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 17:26 WARNING in ath9k_hif_usb_alloc_urbs/usb_submit_urb syzbot
2023-01-30 16:04 ` 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=0000000000001ca15605f37d5ec6@google.com \
--to=syzbot+d625c772c7814faabef9@syzkaller.appspotmail.com \
--cc=andreyknvl@google.com \
--cc=bxb5544@psu.edu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=ingrassia@epigenesys.com \
--cc=khoroshilov@ispras.ru \
--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=pchelkin@ispras.ru \
--cc=quic_kvalo@quicinc.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.