From: syzbot <syzbot+list291bd82fd4f9cf97dab3@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 (Feb 2025)
Date: Thu, 20 Feb 2025 11:03:23 -0800 [thread overview]
Message-ID: <67b77c7b.050a0220.14d86d.02f6.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, 0 new issues were detected and 0 were fixed.
In total, 32 issues are still open and 280 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 21436 Yes possible deadlock in trie_delete_elem
https://syzkaller.appspot.com/bug?extid=9d95beb2a3c260622518
<2> 2116 Yes WARNING in bpf_map_lookup_percpu_elem
https://syzkaller.appspot.com/bug?extid=dce5aae19ae4d6399986
<3> 1993 Yes possible deadlock in __bpf_ringbuf_reserve
https://syzkaller.appspot.com/bug?extid=850aaf14624dc0c6d366
<4> 232 Yes INFO: rcu detected stall in sys_clone (8)
https://syzkaller.appspot.com/bug?extid=c4c6c3dc10cc96bcf723
<5> 177 Yes possible deadlock in __queue_map_get
https://syzkaller.appspot.com/bug?extid=8bdfc2c53fb2b63e1871
<6> 71 Yes possible deadlock in queue_stack_map_push_elem
https://syzkaller.appspot.com/bug?extid=252bc5c744d0bba917e1
<7> 52 Yes possible deadlock in __stack_map_get
https://syzkaller.appspot.com/bug?extid=dddd99ae26c656485d89
<8> 32 Yes INFO: rcu detected stall in sys_unshare (9)
https://syzkaller.appspot.com/bug?extid=872bccd9a68c6ba47718
<9> 23 Yes BUG: MAX_STACK_TRACE_ENTRIES too low! (4)
https://syzkaller.appspot.com/bug?extid=c6c4861455fdd207f160
<10> 16 Yes INFO: rcu detected stall in task_numa_work (2)
https://syzkaller.appspot.com/bug?extid=06d48cbf3e767907cec2
---
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:[~2025-02-20 19:03 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=67b77c7b.050a0220.14d86d.02f6.GAE@google.com \
--to=syzbot+list291bd82fd4f9cf97dab3@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