From: syzbot <syzbot+listbab5e5abece11c828361@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 (Oct 2025)
Date: Mon, 06 Oct 2025 10:29:27 -0700 [thread overview]
Message-ID: <68e3fc77.a70a0220.160221.0005.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, 2 new issues were detected and 3 were fixed.
In total, 23 issues are still open and 309 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3880 Yes WARNING in reg_bounds_sanity_check (2)
https://syzkaller.appspot.com/bug?extid=c950cc277150935cc0b5
<2> 984 Yes WARNING in trace_suspend_resume
https://syzkaller.appspot.com/bug?extid=99d4fec338b62b703891
<3> 94 No INFO: task hung in dev_map_free (3)
https://syzkaller.appspot.com/bug?extid=9bb2e1829da8582dcffa
<4> 45 Yes BUG: sleeping function called from invalid context in sock_map_delete_elem
https://syzkaller.appspot.com/bug?extid=1f1fbecb9413cdbfbef8
<5> 36 Yes general protection fault in __pcpu_freelist_pop
https://syzkaller.appspot.com/bug?extid=331f5bebb641724ff1f0
<6> 18 No KCSAN: data-race in __htab_map_lookup_elem / bpf_lru_pop_free
https://syzkaller.appspot.com/bug?extid=ad4661d6ca888ce7fe11
<7> 4 No WARNING in sock_hash_delete_elem (2)
https://syzkaller.appspot.com/bug?extid=ca62aaf39105978cd946
<8> 2 No possible deadlock in xdp_umem_pin_pages
https://syzkaller.appspot.com/bug?extid=1b607ee7794bdba65be7
---
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-10-06 17:29 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=68e3fc77.a70a0220.160221.0005.GAE@google.com \
--to=syzbot+listbab5e5abece11c828361@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