From: syzbot <syzbot+list076b173dc0214a44347c@syzkaller.appspotmail.com>
To: krzysztof.kozlowski@linaro.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly nfc report (Apr 2024)
Date: Mon, 15 Apr 2024 02:23:17 -0700 [thread overview]
Message-ID: <000000000000f8e62006161f2bf5@google.com> (raw)
Hello nfc maintainers/developers,
This is a 31-day syzbot report for the nfc subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/nfc
During the period, 1 new issues were detected and 3 were fixed.
In total, 11 issues are still open and 24 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1024 Yes INFO: task hung in rfkill_global_led_trigger_worker (2)
https://syzkaller.appspot.com/bug?extid=2e39bc6569d281acbcfb
<2> 167 Yes INFO: task hung in nfc_rfkill_set_block
https://syzkaller.appspot.com/bug?extid=3e3c2f8ca188e30b1427
<3> 45 Yes INFO: task hung in nfc_targets_found
https://syzkaller.appspot.com/bug?extid=2b131f51bb4af224ab40
<4> 33 No INFO: task hung in nfc_urelease_event_work
https://syzkaller.appspot.com/bug?extid=e9e054e7ec32ca9f70da
<5> 26 Yes INFO: task hung in rfkill_sync_work
https://syzkaller.appspot.com/bug?extid=9ef743bba3a17c756174
<6> 15 Yes INFO: task hung in rfkill_unregister (3)
https://syzkaller.appspot.com/bug?extid=bb540a4bbfb4ae3b425d
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2024-04-15 9:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000f8e62006161f2bf5@google.com \
--to=syzbot+list076b173dc0214a44347c@syzkaller.appspotmail.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).