syzbot


witness: reversal: fdlock inode

Status: upstream: reported on 2025/02/09 19:15
Reported-by: syzbot+322a1e0d9e9448762d80@syzkaller.appspotmail.com
First crash: 71d, last: 18d

Sample crash report:
witness: lock order reversal:
 1st 0xfffffd806be45468 fdlock (&newfdp->fd_fd.fd_lock)
 2nd 0xfffffd806dde0748 inode (&ip->i_lock)

OpenBSD/amd64 (ci-openbsd-multicore-7.us-central1-b.c.syzkaller.internal) (tty00)

login: set $lines = 0
SYZFAIL: failed to send rpc
fd=3 want=896 sent=0 n=-1 (errno 32: Broken pipe)
Password:set $maxwidth = 0
Login incorrect
login: show panic
Password:trace
Login incorrect
login: show registers
Password:show proc
Login incorrect
login: ps
Password:show all locks
Login incorrect
show malloc
login: Password:show all pools
Login incorrect
machine ddbcpu 0
login: Password:

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/03 12:23 openbsd 106a406f22e5 996a9618 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore witness: reversal: fdlock inode
2025/04/02 22:12 openbsd 351a734b4a2d b0cc4801 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore witness: reversal: fdlock inode
2025/02/09 19:14 openbsd d2e1daa0feb7 ef44b750 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore witness: reversal: fdlock inode
* Struck through repros no longer work on HEAD.