syzbot


Instances [tested repos]:
Name Last active Uptime Corpus Coverage 🛈 Crashes Execs Kernel build syzkaller build Bugs
Commit Config Freshness Status Commit Freshness Status All Only
ci-upstream-linux-next-kasan-gce-root now 2h41m 55060 540543 340 1000214 5c73cd9f0819 .config 1d00h ab40da58 3h07m all only
Applied filters: Manager=ci-upstream-linux-next-kasan-gce-root (drop) Label=subsystems:hfs (drop)
Extra filters: [With Repro] [With AI Patch Pending Review]
open (15) 🔗
Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Discussions
INFO: task hung in hfsplus_find_init (3) prio:high hfs 1 C error error 43 62d 340d 💬 1 [66d]
INFO: task hung in hfs_mdb_commit (3) prio:high hfs 1 C error done 23 1d07h 390d
possible deadlock in hfsplus_file_extend (2) prio:normal hfs 4 C inconclusive error 912 15d 604d 💬 3 [4d01h]
INFO: task hung in deactivate_super (3) prio:high hfs 1 C done error 105 25d 727d 💬 3 [35d]
possible deadlock in hfs_extend_file (3) hfs 4 C unreliable 5774 1d15h 810d PATCH [806d]
INFO: task hung in hfs_find_init (2) hfs 1 C error error 51 17d 899d 💬 1 [898d]
KMSAN: uninit-value in hfsplus_rename_cat hfs 8 C inconclusive error 1869 16h02m 1001d PATCH [81d]
KASAN: wild-memory-access Read in hfsplus_bnode_dump hfs 19 C error error 471 64d 1178d PATCH [314d]
possible deadlock in hfs_find_init (2) prio:high hfs 4 C error 7968 2d11h 1289d
possible deadlock in hfsplus_find_init prio:high hfs 4 C error error 1052 2d17h 1294d
possible deadlock in hfsplus_block_allocate hfs 4 C done error 433 38d 1317d
possible deadlock in hfsplus_block_free hfs 4 C inconclusive error 394 13d 1317d
kernel BUG in hfs_write_inode prio:high hfs -1 C error 221368 now 1321d PATCH [14h17m]
possible deadlock in hfsplus_get_block prio:high hfs 4 C error 15642 5h35m 1321d
WARNING in hfs_bnode_create prio:high hfs -1 C done error 10880 13h00m 3017d PATCH [76d]
moderation (1) 🔗
Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Discussions
corrupted report (2) prio:low hfs -1 1133590 11m 3010d