From: syzbot <syzbot+list632c08477db437fb3a68@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 (Dec 2024)
Date: Thu, 19 Dec 2024 13:40:24 -0800 [thread overview]
Message-ID: <676492c8.050a0220.1dcc64.003a.GAE@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, 3 new issues were detected and 3 were fixed.
In total, 42 issues are still open and 279 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 23132 Yes WARNING: locking bug in trie_delete_elem
https://syzkaller.appspot.com/bug?extid=b506de56cbbb63148c33
<2> 21422 Yes possible deadlock in trie_delete_elem
https://syzkaller.appspot.com/bug?extid=9d95beb2a3c260622518
<3> 2116 Yes WARNING in bpf_map_lookup_percpu_elem
https://syzkaller.appspot.com/bug?extid=dce5aae19ae4d6399986
<4> 1710 Yes possible deadlock in __bpf_ringbuf_reserve
https://syzkaller.appspot.com/bug?extid=850aaf14624dc0c6d366
<5> 1352 Yes WARNING in format_decode (3)
https://syzkaller.appspot.com/bug?extid=e2c932aec5c8a6e1d31c
<6> 311 Yes KMSAN: uninit-value in ___bpf_prog_run (4)
https://syzkaller.appspot.com/bug?extid=853242d9c9917165d791
<7> 182 Yes INFO: rcu detected stall in sys_clone (8)
https://syzkaller.appspot.com/bug?extid=c4c6c3dc10cc96bcf723
<8> 173 Yes UBSAN: array-index-out-of-bounds in bpf_prog_select_runtime
https://syzkaller.appspot.com/bug?extid=d2a2c639d03ac200a4f1
<9> 166 Yes possible deadlock in __queue_map_get
https://syzkaller.appspot.com/bug?extid=8bdfc2c53fb2b63e1871
<10> 92 Yes WARNING in bpf_get_stack_raw_tp
https://syzkaller.appspot.com/bug?extid=ce35de20ed6652f60652
---
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-12-19 21:40 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=676492c8.050a0220.1dcc64.003a.GAE@google.com \
--to=syzbot+list632c08477db437fb3a68@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