From: syzbot <syzbot+3e3c2f8ca188e30b1427@syzkaller.appspotmail.com>
To: brauner@kernel.org, broonie@kernel.org, catalin.marinas@arm.com,
davem@davemloft.net, edumazet@google.com, faenkhauser@gmail.com,
hdanton@sina.com, krzysztof.kozlowski@linaro.org,
kuba@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-nfc@lists.01.org,
luiz.von.dentz@intel.com, madvenka@linux.microsoft.com,
netdev@vger.kernel.org, pabeni@redhat.com,
scott@os.amperecomputing.com, syzkaller-bugs@googlegroups.com,
will@kernel.org
Subject: Re: [syzbot] [nfc?] INFO: task hung in nfc_rfkill_set_block
Date: Tue, 23 May 2023 22:43:26 -0700 [thread overview]
Message-ID: <00000000000098aa2305fc69fb67@google.com> (raw)
In-Reply-To: <000000000000959f6b05ed853d12@google.com>
syzbot has bisected this issue to:
commit 7ac7267fad5908476b357e7e9813d23516c2b0a1
Author: Fae <faenkhauser@gmail.com>
Date: Sun Jul 24 18:25:02 2022 +0000
Bluetooth: Add VID/PID 0489/e0e0 for MediaTek MT7921
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1523596a280000
start commit: ae8373a5add4 Merge tag 'x86_urgent_for_6.4-rc4' of git://g..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1723596a280000
console output: https://syzkaller.appspot.com/x/log.txt?x=1323596a280000
kernel config: https://syzkaller.appspot.com/x/.config?x=927d4df6d674370e
dashboard link: https://syzkaller.appspot.com/bug?extid=3e3c2f8ca188e30b1427
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1099e2c5280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=113f66b1280000
Reported-by: syzbot+3e3c2f8ca188e30b1427@syzkaller.appspotmail.com
Fixes: 7ac7267fad59 ("Bluetooth: Add VID/PID 0489/e0e0 for MediaTek MT7921")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2023-05-24 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000959f6b05ed853d12@google.com>
2023-05-24 5:43 ` syzbot [this message]
2023-11-21 10:55 ` [syzbot] [net?] [nfc?] INFO: task hung in nfc_rfkill_set_block syzbot
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=00000000000098aa2305fc69fb67@google.com \
--to=syzbot+3e3c2f8ca188e30b1427@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=faenkhauser@gmail.com \
--cc=hdanton@sina.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfc@lists.01.org \
--cc=luiz.von.dentz@intel.com \
--cc=madvenka@linux.microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=scott@os.amperecomputing.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.org \
/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).