From: syzbot <syzbot+list2edbf5245474e3beec7a@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 (Aug 2024)
Date: Wed, 14 Aug 2024 05:43:23 -0700 [thread overview]
Message-ID: <000000000000633cf1061fa4125b@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, 2 new issues were detected and 6 were fixed.
In total, 48 issues are still open and 269 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 19123 Yes possible deadlock in trie_delete_elem
https://syzkaller.appspot.com/bug?extid=9d95beb2a3c260622518
<2> 13875 Yes KASAN: slab-out-of-bounds Read in btf_datasec_check_meta
https://syzkaller.appspot.com/bug?extid=cc32304f6487ebff9b70
<3> 8937 Yes possible deadlock in task_fork_fair
https://syzkaller.appspot.com/bug?extid=1a93ee5d329e97cfbaff
<4> 1885 Yes WARNING in bpf_map_lookup_percpu_elem
https://syzkaller.appspot.com/bug?extid=dce5aae19ae4d6399986
<5> 1371 Yes possible deadlock in __bpf_ringbuf_reserve
https://syzkaller.appspot.com/bug?extid=850aaf14624dc0c6d366
<6> 336 Yes general protection fault in dev_map_enqueue (2)
https://syzkaller.appspot.com/bug?extid=cca39e6e84a367a7e6f6
<7> 199 Yes KMSAN: uninit-value in ___bpf_prog_run (4)
https://syzkaller.appspot.com/bug?extid=853242d9c9917165d791
<8> 147 Yes possible deadlock in __queue_map_get
https://syzkaller.appspot.com/bug?extid=8bdfc2c53fb2b63e1871
<9> 102 No possible deadlock in trie_update_elem
https://syzkaller.appspot.com/bug?extid=ea624e536fee669a05cf
<10> 77 Yes INFO: rcu detected stall in sys_openat (3)
https://syzkaller.appspot.com/bug?extid=23d96fb466ad56cbb5e5
---
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-08-14 12:43 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=000000000000633cf1061fa4125b@google.com \
--to=syzbot+list2edbf5245474e3beec7a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.