Re: assert failed: lktype != LK_NONE

To: riastradh%NetBSD.org@localhost, syzkaller-netbsd-bugs%googlegroups.com@localhost
Subject: Re: assert failed: lktype != LK_NONE
From: syzbot <syzbot+da4be777819055325902%syzkaller.appspotmail.com@localhost>
Date: Sun, 17 Jul 2022 18:38:21 -0700

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.

-- 
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/0000000000004a71da05e40a6c15%40google.com.

Follow-Ups:
- Re: assert failed: lktype != LK_NONE
  - From: Taylor R Campbell

Prev by Date: panic: ASan: Unauthorized Access In ADDR: Addr ADDR [NUM bytes, read, PoolUseAfterFree]
Next by Date: Re: assert failed: lktype != LK_NONE
Previous by Thread: panic: ASan: Unauthorized Access In ADDR: Addr ADDR [NUM bytes, read, PoolUseAfterFree]
Next by Thread: Re: assert failed: lktype != LK_NONE
Indexes:

Home | Main Index | Thread Index | Old Index