syzbot


panic: ffs_update: bad link cnt

Status: auto-obsoleted due to no activity on 2023/09/14 15:36
Reported-by: syzbot+6bcfdf7f8142bcbb89c6@syzkaller.appspotmail.com
First crash: 778d, last: 276d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
openbsd panic: ffs_update: bad link cnt (2) 4 57d 182d 0/3 upstream: reported on 2023/09/18 11:32

Sample crash report:
syncing disks...panic: ffs_update: bad link cnt
Starting stack trace...
panic(ffffffff82836d7a) at panic+0x16f sys/kern/subr_prf.c:229
ffs_update(fffffd8066272890,0) at ffs_update+0x313 sys/ufs/ffs/ffs_inode.c:101
VOP_FSYNC(fffffd8067d5b990,fffffd807f7d77b8,2,ffff8000212f1b50) at VOP_FSYNC+0xd2 sys/kern/vfs_vops.c:311
ffs_sync_vnode(fffffd8067d5b990,ffff8000212e66e0) at ffs_sync_vnode+0x184 sys/ufs/ffs/ffs_vfsops.c:1197
vfs_mount_foreach_vnode(ffff8000006d8c00,ffffffff81869010,ffff8000212e66e0) at vfs_mount_foreach_vnode+0x55 sys/kern/vfs_subr.c:910
ffs_sync(ffff8000006d8c00,2,0,fffffd807f7d77b8,ffff8000212f1b50) at ffs_sync+0x11f sys/ufs/ffs/ffs_vfsops.c:1248
sys_sync(ffff8000212f1b50,0,0) at sys_sync+0xbc sys/kern/vfs_syscalls.c:537
vfs_syncwait(ffff8000212f1b50,1) at vfs_syncwait+0x3a
vfs_shutdown(ffff8000212f1b50) at vfs_shutdown+0x61 sys/kern/vfs_subr.c:1791
boot(100) at boot+0xcc sys/arch/amd64/amd64/machdep.c:843
reboot(100) at reboot+0x84
panic(ffffffff82787683) at panic+0x18f sys/kern/subr_prf.c:231
vop_generic_badop(ffff8000212e69a8) at vop_generic_badop+0x1f sys/kern/vfs_default.c:133
VOP_STRATEGY(fffffd8067ccd7d0,fffffd8067a3e7e0) at VOP_STRATEGY+0x9f sys/kern/vfs_vops.c:628
bwrite(fffffd8067a3e7e0) at bwrite+0x1f4 sys/kern/vfs_bio.c:760
VOP_BWRITE(fffffd8067a3e7e0) at VOP_BWRITE+0x4e sys/kern/vfs_vops.c:640
ufs_mkdir(ffff8000212e6c40) at ufs_mkdir+0x6c4 sys/ufs/ufs/ufs_vnops.c:1235
VOP_MKDIR(fffffd8067ab48a0,ffff8000212e6da0,ffff8000212e6dd0,ffff8000212e6cd0) at VOP_MKDIR+0xc3 sys/kern/vfs_vops.c:388
domkdirat(ffff8000212f1b50,ffffff9c,7428e0617130,1ff) at domkdirat+0x125 sys/kern/vfs_syscalls.c:3074
syscall(ffff8000212e6f50) at syscall+0x5e2 mi_syscall sys/sys/syscall_mi.h:110 [inline]
syscall(ffff8000212e6f50) at syscall+0x5e2 sys/arch/amd64/amd64/trap.c:632
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7428e06171a0, count: 236
End of stack trace.

dump to dev 4,1 not possible
rpanebioco:t iknegr.nel..
 diagnosticSeaBIOS (version 1.8.2-google)
Total RAM Size = 0x0000000080000000 = 2048 MiB
CPUs found: 2     Max CPUs supported: 2
SeaBIOS (version 1.8.2-google)
Machine UUID 68bf758f-d7e1-83a6-91e2-c70932eb46bc
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=4194304 = 2048 MiB
drive 0x000f2850: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Sending Seabios boot VM event.
Booting from Hard Disk 0...
>> OpenBSD/amd64 BOOT 3.56
boot> set $lines = 0
set: syntax error
boot> set $maxwidth = 0
set: syntax error
boot> show panic
boot: illegal argument panic
boot> trace
boot> show registers
boot> show proc
boot> ps
boot> show all locks
boot> show malloc
boot> show all pools
boot> machine ddbcpu 0
machine: syntax error
boot> trace
boot> machine ddbcpu 1
machine: syntax error
boot> trace

Crashes (18):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/06/16 15:36 openbsd d87ad1f5ae73 f3921d4d .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: ffs_update: bad link cnt
2023/04/16 18:38 openbsd 1e5b016c5082 3cfcaa1b .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: ffs_update: bad link cnt
2023/04/09 17:27 openbsd 1e5b016c5082 71147e29 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main panic: ffs_update: bad link cnt
2023/04/04 06:39 openbsd 1e5b016c5082 7db618d0 .config console log report ci-openbsd-main panic: ffs_update: bad link cnt
2023/02/02 06:32 openbsd b6a2b665f44a 16d19e30 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main panic: ffs_update: bad link cnt
2023/01/12 02:41 openbsd 86a45bbd35a5 96166539 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: ffs_update: bad link cnt
2022/10/28 01:27 openbsd 5cc83d08f96f 5c716ff6 .config console log report ci-openbsd-main panic: ffs_update: bad link cnt
2022/10/24 19:02 openbsd 214e94d30852 ff2fe65d .config console log report ci-openbsd-main panic: ffs_update: bad link cnt
2022/10/03 17:54 openbsd 5db73e2946db feb56351 .config console log report ci-openbsd-main panic: ffs_update: bad link cnt
2022/09/06 22:22 openbsd 0d9be21fa6ac 5fc30c37 .config console log report ci-openbsd-multicore panic: ffs_update: bad link cnt
2022/08/18 00:42 openbsd 4a99c7448f02 a9409d47 .config console log report ci-openbsd-multicore panic: ffs_update: bad link cnt
2022/07/08 10:17 openbsd 794feedc7a05 8442e655 .config console log report ci-openbsd-main panic: ffs_update: bad link cnt
2022/05/22 05:16 openbsd b46cfa51b3d3 7268fa62 .config console log report ci-openbsd-main panic: ffs_update: bad link cnt
2022/04/16 23:48 openbsd 01ac1ae112e9 8bcc32a6 .config console log report ci-openbsd-main panic: ffs_update: bad link cnt
2022/03/03 21:50 openbsd 0d6a9aa9baac 45a13a73 .config console log report ci-openbsd-main panic: ffs_update: bad link cnt
2022/02/27 11:44 openbsd dd2bb77956f6 45a13a73 .config console log report ci-openbsd-main panic: ffs_update: bad link cnt
2022/02/25 04:21 openbsd 1e79788ede5c 7c337266 .config console log report ci-openbsd-main panic: ffs_update: bad link cnt
2022/01/30 18:27 openbsd 8b422bc70c2d 495e00c5 .config console log report ci-openbsd-multicore panic: ffs_update: bad link cnt
* Struck through repros no longer work on HEAD.