Re: assert failed: lktype != LK_NONE

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

> Date: Sun, 17 Jul 2022 18:38:21 -0700
> From: syzbot <syzbot+da4be777819055325902%syzkaller.appspotmail.com@localhost>
> 
> This bug is marked as fixed by commit:
> Fix mistake in error branch locking caused by previous changes.
> But I can't find it in any tested tree for more than 90 days.
> Is it a correct commit? Please update it by replying:
> #syz fix: exact-commit-title
> Until then the bug is still considered open and
> new crashes with the same signature are ignored.

Confused -- here's the commit:

https://mail-index.netbsd.org/source-changes/2022/04/16/msg138070.html
https://github.com/netbsd/src/commit/fba7f3f9c8fd4ef9e9a97d8f2c3aa06f5426edb8

What I wrote in the syzbot command was:

#syz fix: Fix mistake in error branch locking caused by previous changes.

What did I do wrong?

-- 
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/20220718081352.A0AA660A2D%40jupiter.mumble.net.