From: syzbot <syzbot+lista9d8cacda29a45932ea0@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 (May 2024)
Date: Sun, 12 May 2024 11:21:31 -0700 [thread overview]
Message-ID: <00000000000087c944061845d62e@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, 13 new issues were detected and 2 were fixed.
In total, 44 issues are still open and 238 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 52469 Yes possible deadlock in console_flush_all (2)
https://syzkaller.appspot.com/bug?extid=f78380e4eae53c64125c
<2> 15516 Yes possible deadlock in trie_delete_elem
https://syzkaller.appspot.com/bug?extid=9d95beb2a3c260622518
<3> 8620 Yes possible deadlock in task_fork_fair
https://syzkaller.appspot.com/bug?extid=1a93ee5d329e97cfbaff
<4> 6553 Yes KASAN: slab-out-of-bounds Read in btf_datasec_check_meta
https://syzkaller.appspot.com/bug?extid=cc32304f6487ebff9b70
<5> 1615 Yes WARNING in skb_ensure_writable
https://syzkaller.appspot.com/bug?extid=0c4150bff9fff3bf023c
<6> 496 Yes possible deadlock in sock_map_delete_elem
https://syzkaller.appspot.com/bug?extid=4ac2fe2b496abca8fa4b
<7> 241 Yes WARNING in bpf_map_lookup_percpu_elem
https://syzkaller.appspot.com/bug?extid=dce5aae19ae4d6399986
<8> 224 No KASAN: slab-use-after-free Read in htab_map_alloc (2)
https://syzkaller.appspot.com/bug?extid=061f58eec3bde7ee8ffa
<9> 137 Yes KMSAN: uninit-value in ___bpf_prog_run (4)
https://syzkaller.appspot.com/bug?extid=853242d9c9917165d791
<10> 107 Yes WARNING in sock_map_close
https://syzkaller.appspot.com/bug?extid=07a2e4a1a57118ef7355
---
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-05-12 18:21 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=00000000000087c944061845d62e@google.com \
--to=syzbot+lista9d8cacda29a45932ea0@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