From: syzbot <syzbot+listb569d2a8a4e132119665@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 (Sep 2023)
Date: Wed, 06 Sep 2023 01:12:21 -0700 [thread overview]
Message-ID: <0000000000008253550604ac4d36@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, 0 new issues were detected and 0 were fixed.
In total, 13 issues are still open and 17 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 585 Yes INFO: task hung in rfkill_global_led_trigger_worker (2)
https://syzkaller.appspot.com/bug?extid=2e39bc6569d281acbcfb
<2> 116 Yes BUG: corrupted list in nfc_llcp_unregister_device
https://syzkaller.appspot.com/bug?extid=81232c4a81a886e2b580
<3> 106 Yes BUG: corrupted list in nfc_llcp_register_device
https://syzkaller.appspot.com/bug?extid=c1d0a03d305972dbbe14
<4> 80 Yes INFO: task hung in nfc_rfkill_set_block
https://syzkaller.appspot.com/bug?extid=3e3c2f8ca188e30b1427
<5> 16 Yes INFO: task hung in rfkill_sync_work
https://syzkaller.appspot.com/bug?extid=9ef743bba3a17c756174
<6> 5 Yes UBSAN: shift-out-of-bounds in nci_activate_target
https://syzkaller.appspot.com/bug?extid=0839b78e119aae1fec78
<7> 2 Yes memory leak in skb_copy (2)
https://syzkaller.appspot.com/bug?extid=6eb09d75211863f15e3e
<8> 1 Yes memory leak in virtual_ncidev_write (2)
https://syzkaller.appspot.com/bug?extid=6b7c68d9c21e4ee4251b
---
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:[~2023-09-06 8:12 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=0000000000008253550604ac4d36@google.com \
--to=syzbot+listb569d2a8a4e132119665@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).