From: syzbot <syzbot+9ef743bba3a17c756174@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, hdanton@sina.com,
johannes@sipsolutions.net, krzysztof.kozlowski@canonical.com,
krzysztof.kozlowski@linaro.org, kuba@kernel.org,
linma@zju.edu.cn, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: task hung in rfkill_sync_work
Date: Thu, 26 Jan 2023 06:18:16 -0800 [thread overview]
Message-ID: <00000000000080d62605f32b6bcb@google.com> (raw)
In-Reply-To: <000000000000788a6905f0c06160@google.com>
syzbot has bisected this issue to:
commit 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102
Author: Lin Ma <linma@zju.edu.cn>
Date: Tue Nov 16 15:26:52 2021 +0000
NFC: reorder the logic in nfc_{un,}register_device
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=110cbe1e480000
start commit: 9d2f6060fe4c Merge tag 'trace-v6.2-1' of git://git.kernel...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=130cbe1e480000
console output: https://syzkaller.appspot.com/x/log.txt?x=150cbe1e480000
kernel config: https://syzkaller.appspot.com/x/.config?x=85327a149d5f50f
dashboard link: https://syzkaller.appspot.com/bug?extid=9ef743bba3a17c756174
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156edba0480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15556074480000
Reported-by: syzbot+9ef743bba3a17c756174@syzkaller.appspotmail.com
Fixes: 3e3b5dfcd16a ("NFC: reorder the logic in nfc_{un,}register_device")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-01-26 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 19:45 [syzbot] INFO: task hung in rfkill_sync_work syzbot
2022-12-26 19:47 ` Johannes Berg
2023-01-26 14:18 ` 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=00000000000080d62605f32b6bcb@google.com \
--to=syzbot+9ef743bba3a17c756174@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=johannes@sipsolutions.net \
--cc=krzysztof.kozlowski@canonical.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linma@zju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.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).