syzbot


panic: vputonfreelist: lock count is not zero
Status: fixed on 2020/03/27 17:30
Reported-by: syzbot+767d6deb1a647850a0ca@syzkaller.appspotmail.com
Fix commit: 2a9890d8c8d9 Relax the lockcount assertion in vputonfreelist(). Back when I fixed several problems with the vnode exclusive lock implementation, I overlooked the fact that a vnode can be in a state where the usecount is zero while the holdcount still being positive. There could still be threads waiting on the vnode lock in uvn_io() as long as the holdcount is positive.
First crash: 514d, last: 514d
Patch testing requests:
Created Duration User Patch Repo Result
2020/02/29 09:30 20m anton@basename.se https://github.com/mptre/openbsd-src syzkaller OK

Sample crash report:

Crashes (2):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-openbsd-multicore 2020/02/28 04:47 openbsd c6faab6d3d04 c88c7b75 .config log report syz C
ci-openbsd-multicore 2020/02/28 03:45 openbsd c6faab6d3d04 c88c7b75 .config log report