syzbot


panic: ffs_update: bad link cnt

Status: upstream: reported on 2022/01/30 18:28
Reported-by: syzbot+6bcfdf7f8142bcbb89c6@syzkaller.appspotmail.com
First crash: 367d, last: 6h23m

Sample crash report:
syncing disks...panic: ffs_update: bad link cnt
Starting stack trace...
panic(ffffffff827c7b31) at panic+0x155 sys/kern/subr_prf.c:229
ffs_update(fffffd807b9e90f0,0) at ffs_update+0x303 sys/ufs/ffs/ffs_inode.c:101
VOP_FSYNC(fffffd806489b468,fffffd807f7d79c0,2,ffff8000fffea038) at VOP_FSYNC+0xc5 sys/kern/vfs_vops.c:311
ffs_sync_vnode(fffffd806489b468,ffff800021725aa0) at ffs_sync_vnode+0x180 sys/ufs/ffs/ffs_vfsops.c:1197
vfs_mount_foreach_vnode(ffff8000006db000,ffffffff82137070,ffff800021725aa0) at vfs_mount_foreach_vnode+0x55 sys/kern/vfs_subr.c:910
ffs_sync(ffff8000006db000,2,0,fffffd807f7d79c0,ffff8000fffea038) at ffs_sync+0x11f sys/ufs/ffs/ffs_vfsops.c:1248
sys_sync(ffff8000fffea038,0,0) at sys_sync+0xbc sys/kern/vfs_syscalls.c:537
vfs_syncwait(ffff8000fffea038,1) at vfs_syncwait+0x36
vfs_shutdown(ffff8000fffea038) at vfs_shutdown+0x5d sys/kern/vfs_subr.c:1791
boot(100) at boot+0xbb sys/arch/amd64/amd64/machdep.c:843
reboot(100) at reboot+0x77
panic(ffffffff8271a161) at panic+0x175 sys/kern/subr_prf.c:231
vop_generic_badop(ffff800021725d58) at vop_generic_badop+0x1b sys/kern/vfs_default.c:133
VOP_STRATEGY(fffffd807e045cb8,fffffd8066458398) at VOP_STRATEGY+0x9b sys/kern/vfs_vops.c:628
bwrite(fffffd8066458398) at bwrite+0x1e7 sys/kern/vfs_bio.c:760
VOP_BWRITE(fffffd8066458398) at VOP_BWRITE+0x4a sys/kern/vfs_vops.c:640
ufs_mkdir(ffff800021725ff0) at ufs_mkdir+0x6b4 sys/ufs/ufs/ufs_vnops.c:1236
VOP_MKDIR(fffffd807ab94ca8,ffff800021726150,ffff800021726180,ffff800021726080) at VOP_MKDIR+0xbf sys/kern/vfs_vops.c:388
domkdirat(ffff8000fffea038,ffffff9c,7f7fffffb7d0,1ff) at domkdirat+0x121 sys/kern/vfs_syscalls.c:3112
syscall(ffff800021726300) at syscall+0x4e6 sys/arch/amd64/amd64/trap.c:626
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7f7fffffb840, count: 236
End of stack trace.

dump to dev 4,1 not possible
rebooting...
SeaBIOS (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 2aab0ffc-1c4c-a86f-044c-3bdb0702e43a
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 0x000f27d0: 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.55
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 (14):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci-openbsd-main 2023/02/02 06:32 openbsd b6a2b665f44a 16d19e30 .config console log report [disk image] [bsd.gdb] [kernel image] panic: ffs_update: bad link cnt
ci-openbsd-multicore 2023/01/12 02:41 openbsd 86a45bbd35a5 96166539 .config console log report [disk image] [bsd.gdb] [kernel image] panic: ffs_update: bad link cnt
ci-openbsd-main 2022/10/28 01:27 openbsd 5cc83d08f96f 5c716ff6 .config console log report [disk image] [bsd.gdb] [kernel image] panic: ffs_update: bad link cnt
ci-openbsd-main 2022/10/24 19:02 openbsd 214e94d30852 ff2fe65d .config console log report [disk image] [bsd.gdb] [kernel image] panic: ffs_update: bad link cnt
ci-openbsd-main 2022/10/03 17:54 openbsd 5db73e2946db feb56351 .config console log report [disk image] [bsd.gdb] [kernel image] panic: ffs_update: bad link cnt
ci-openbsd-multicore 2022/09/06 22:22 openbsd 0d9be21fa6ac 5fc30c37 .config console log report panic: ffs_update: bad link cnt
ci-openbsd-multicore 2022/08/18 00:42 openbsd 4a99c7448f02 a9409d47 .config console log report panic: ffs_update: bad link cnt
ci-openbsd-main 2022/07/08 10:17 openbsd 794feedc7a05 8442e655 .config console log report panic: ffs_update: bad link cnt
ci-openbsd-main 2022/05/22 05:16 openbsd b46cfa51b3d3 7268fa62 .config console log report panic: ffs_update: bad link cnt
ci-openbsd-main 2022/04/16 23:48 openbsd 01ac1ae112e9 8bcc32a6 .config console log report panic: ffs_update: bad link cnt
ci-openbsd-main 2022/03/03 21:50 openbsd 0d6a9aa9baac 45a13a73 .config console log report panic: ffs_update: bad link cnt
ci-openbsd-main 2022/02/27 11:44 openbsd dd2bb77956f6 45a13a73 .config console log report panic: ffs_update: bad link cnt
ci-openbsd-main 2022/02/25 04:21 openbsd 1e79788ede5c 7c337266 .config console log report panic: ffs_update: bad link cnt
ci-openbsd-multicore 2022/01/30 18:27 openbsd 8b422bc70c2d 495e00c5 .config console log report panic: ffs_update: bad link cnt
* Struck through repros no longer work on HEAD.