assert failed: lktype != LK_NONE

To: syzbot+da4be777819055325902%syzkaller.appspotmail.com@localhost
Subject: assert failed: lktype != LK_NONE
From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
Date: Mon, 15 Aug 2022 08:40:59 +0000

#syz fix: Fix mistake in error branch locking caused by previous changes. vput(vp) also unlocks vp, thus unlocking happens twice in error flow causing kernel to panic with failed assertion lktype != LK_NONE in vfs_vnode.c#778. Thanks riastradh with finding the issue.

https://mail-index.netbsd.org/source-changes/2022/04/16/msg138070.html
https://syzkaller.appspot.com/bug?id=a4ca182d4b261abe6f3dafc0d4d5d8a543642ce6

-- 
You received this message because you are subscribed to the Google Groups "syzkaller-netbsd-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-netbsd-bugs+unsubscribe%googlegroups.com@localhost.
To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-netbsd-bugs/20220815084103.9F6C06086C%40jupiter.mumble.net.

Prev by Date: Re: assert failed: lktype != LK_NONE
Next by Date: Re: panic: LOCKDEBUG: Kernel lock error: _kernel_lock,240: spinout
Previous by Thread: Re: assert failed: lktype != LK_NONE
Next by Thread: Re: SYZFAIL: cover mmap failed
Indexes:

Home | Main Index | Thread Index | Old Index