From: syzbot <syzbot+list429d82c8ab7976cd21b4@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly bpf report (Apr 2024)
Date: Wed, 10 Apr 2024 23:54:24 -0700 [thread overview]
Message-ID: <0000000000001d51190615cca0a7@google.com> (raw)
Hello bpf maintainers/developers,
This is a 31-day syzbot report for the bpf subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/bpf
During the period, 24 new issues were detected and 8 were fixed.
In total, 34 issues are still open and 219 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 13092 Yes WARNING in sock_map_delete_elem
https://syzkaller.appspot.com/bug?extid=2f4f478b78801c186d39
<2> 11661 Yes WARNING in sock_hash_delete_elem
https://syzkaller.appspot.com/bug?extid=1c04a1e4ae355870dc7a
<3> 8530 Yes possible deadlock in task_fork_fair
https://syzkaller.appspot.com/bug?extid=1a93ee5d329e97cfbaff
<4> 6100 Yes possible deadlock in trie_delete_elem
https://syzkaller.appspot.com/bug?extid=9d95beb2a3c260622518
<5> 4928 Yes KASAN: slab-out-of-bounds Read in btf_datasec_check_meta
https://syzkaller.appspot.com/bug?extid=cc32304f6487ebff9b70
<6> 1115 No possible deadlock in __lock_task_sighand (2)
https://syzkaller.appspot.com/bug?extid=34267210261c2cbba2da
<7> 731 Yes possible deadlock in scheduler_tick (3)
https://syzkaller.appspot.com/bug?extid=628f63ef3b071e16463e
<8> 414 Yes INFO: rcu detected stall in corrupted (4)
https://syzkaller.appspot.com/bug?extid=aa7d098bd6fa788fae8e
<9> 353 Yes WARNING in format_decode (3)
https://syzkaller.appspot.com/bug?extid=e2c932aec5c8a6e1d31c
<10> 271 No possible deadlock in sock_hash_delete_elem (2)
https://syzkaller.appspot.com/bug?extid=ec941d6e24f633a59172
---
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-11 6:54 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=0000000000001d51190615cca0a7@google.com \
--to=syzbot+list429d82c8ab7976cd21b4@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@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