witness: reversal: lock order data missing (3)

13 views
Skip to first unread message

syzbot

unread,
Mar 15, 2022, 4:04:24 PM3/15/22
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 4141bb4bac68 Check BIO_reset() return value to make gcc ha..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1453f961700000
kernel config: https://syzkaller.appspot.com/x/.config?x=bf87b6915a88cd0d
dashboard link: https://syzkaller.appspot.com/bug?extid=444b020a92d87d6ded8b

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+444b02...@syzkaller.appspotmail.com

witness: lock order reversal:
1st 0xffffffff82981660 pf_lock (pf_lock)
2nd 0xffffffff8291bdd0 netlock (netlock)
lock order "netlock"(rwlock) -> "pf_lock"(rwlock) first seen at:
#0 rw_enter_write+0x5b sys/kern/kern_rwlock.c:128
#1 pfioctl+0x3fba sys/net/pf_ioctl.c:2966
#2 VOP_IOCTL+0x96 sys/kern/vfs_vops.c:264
#3 vn_ioctl+0xbc sys/kern/vfs_vnops.c:531
#4 sys_ioctl+0x4a2
#5 syscall+0x489 mi_syscall sys/sys/syscall_mi.h:102 [inline]
#5 syscall+0x489 sys/arch/amd64/amd64/trap.c:585
#6 Xsyscall+0x128
lock order data w1 -> w2 missing
Stopped at db_enter+0x18: addq $0x8,%rsp


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

Moritz Buhl

unread,
Jul 20, 2022, 2:31:36 PM7/20/22
to syzkaller-openbsd-bugs
#syz fix: Release PF und NET lock before calling copyout for DIOCIGETIFACES.
#syz dup: witness: reversal: pf_lock netlock (3)

looking at the callstack:
copyout() at copyout+0x53 pfioctl(4900,c0284457,ffff80002e2208e0,1,ffff80002121f508) at pfioctl+0x4516 sys/net/pf_ioctl.c:2932
VOP_IOCTL(fffffd806f6828e8,c0284457,ffff80002e2208e0,1,fffffd807f7d7600,ffff80002121f508) at VOP_IOCTL+0x96 sys/kern/vfs_vops.c:264
vn_ioctl(fffffd8065095688,c0284457,ffff80002e2208e0,ffff80002121f508) at vn_ioctl+0xbc sys/kern/vfs_vnops.c:531
sys_ioctl(ffff80002121f508,ffff80002e2209f8,ffff80002e220a50) at sys_ioctl+0x4a2
syscall(ffff80002e220ac0) at syscall+0x489 mi_syscall sys/sys/syscall_mi.h:102
[inline] syscall(ffff80002e220ac0) at syscall+0x489 sys/arch/amd64/amd64/trap.c:585
Xsyscall() at Xsyscall+0x128

DIOCIGETIFACES calls copyout without dropping the locks like in the other problem.

syzbot

unread,
Jul 20, 2022, 2:31:39 PM7/20/22
to 'Moritz Buhl' via syzkaller-openbsd-bugs, syzkaller-o...@googlegroups.com
> #syz fix: Release PF und NET lock before calling copyout for

I see the command but can't find the corresponding bug.
Please resend the email to syzbo...@syzkaller.appspotmail.com address
that is the sender of the bug report (also present in the Reported-by tag).

> DIOCIGETIFACES.
> #syz dup: witness: reversal: pf_lock netlock (3)
>
> looking at the callstack:
> copyout() at copyout+0x53
> pfioctl(4900,c0284457,ffff80002e2208e0,1,ffff80002121f508) at
> pfioctl+0x4516 sys/net/pf_ioctl.c:2932
> <https://github.com/openbsd/src/blob/62198fa5a9d005ca1c651b3df2c33ce50d333b27/sys/net/pf_ioctl.c#L2932>
> VOP_IOCTL(fffffd806f6828e8,c0284457,ffff80002e2208e0,1,fffffd807f7d7600,ffff80002121f508)
> at VOP_IOCTL+0x96 sys/kern/vfs_vops.c:264
> <https://github.com/openbsd/src/blob/62198fa5a9d005ca1c651b3df2c33ce50d333b27/sys/kern/vfs_vops.c#L264>
> vn_ioctl(fffffd8065095688,c0284457,ffff80002e2208e0,ffff80002121f508) at
> vn_ioctl+0xbc sys/kern/vfs_vnops.c:531
> <https://github.com/openbsd/src/blob/62198fa5a9d005ca1c651b3df2c33ce50d333b27/sys/kern/vfs_vnops.c#L531>
> sys_ioctl(ffff80002121f508,ffff80002e2209f8,ffff80002e220a50) at
> sys_ioctl+0x4a2
> syscall(ffff80002e220ac0) at syscall+0x489 mi_syscall
> sys/sys/syscall_mi.h:102
> <https://github.com/openbsd/src/blob/62198fa5a9d005ca1c651b3df2c33ce50d333b27/sys/sys/syscall_mi.h#L102>
> [inline] syscall(ffff80002e220ac0) at syscall+0x489
> sys/arch/amd64/amd64/trap.c:585
> <https://github.com/openbsd/src/blob/62198fa5a9d005ca1c651b3df2c33ce50d333b27/sys/arch/amd64/amd64/trap.c#L585>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-openbsd-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-openbsd...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/abf6a41a-f635-4f78-8dc9-239c10639030n%40googlegroups.com.

Moritz Buhl

unread,
Jul 20, 2022, 3:14:05 PM7/20/22
to syzkaller-openbsd-bugs
#syz fix: Release PF und NET lock before calling copyout for DIOCIGETIFACES. OK sashan@ Reported-by: syzbot+b6afd1...@syzkaller.appspotmail.com    

syzbot schrieb am Mittwoch, 20. Juli 2022 um 20:31:39 UTC+2:
> #syz fix: Release PF und NET lock before calling copyout for

I see the command but can't find the corresponding bug.
Please resend the email to syzbot+HASH@syzkaller.appspotmail.com address
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-openbsd-bugs+unsub...@googlegroups.com.

syzbot

unread,
Jul 20, 2022, 3:14:09 PM7/20/22
to 'Moritz Buhl' via syzkaller-openbsd-bugs, syzkaller-o...@googlegroups.com
> #syz fix: Release PF und NET lock before calling copyout for

I see the command but can't find the corresponding bug.
Please resend the email to syzbo...@syzkaller.appspotmail.com address
that is the sender of the bug report (also present in the Reported-by tag).

> DIOCIGETIFACES. OK sashan@ Reported-by:
> syzbot+b6afd1...@syzkaller.appspotmail.com
>
> syzbot schrieb am Mittwoch, 20. Juli 2022 um 20:31:39 UTC+2:
>
>> > #syz fix: Release PF und NET lock before calling copyout for
>>
>> I see the command but can't find the corresponding bug.
>> Please resend the email to syzbo...@syzkaller.appspotmail.com address
>> an email to syzkaller-openbsd...@googlegroups.com.
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-openbsd-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-openbsd...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/b6e032a8-9e08-4644-99bf-9c09bf0033dbn%40googlegroups.com.

syzbot

unread,
Jul 20, 2022, 3:16:27 PM7/20/22
to Moritz Buhl, morit...@googlemail.com, syzkaller-o...@googlegroups.com
>
>
> ---------- Weitergeleitete Nachricht ---------
> Von: Moritz Buhl <Unbekannt>
> Datum: Mittwoch, 20. Juli 2022 um 20:31:36 UTC+2
> Betreff: Re: witness: reversal: lock order data missing (3)
> An: syzkaller-openbsd-bugs <Unbekannt>
>
>
> #syz fix: Release PF und NET lock before calling copyout for

Your 'fix:' command is accepted, but please keep syzkaller-o...@googlegroups.com mailing list in CC next time. It serves as a history of what happened with each bug report. Thank you.

syzbot

unread,
Oct 18, 2022, 3:16:37 PM10/18/22
to morit...@googlemail.com, syzkaller-o...@googlegroups.com
This bug is marked as fixed by commit:
Release PF und NET lock before calling copyout for
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.

syzbot

unread,
Nov 1, 2022, 3:16:46 PM11/1/22
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Nov 7, 2022, 4:39:41 AM11/7/22
to Moritz Buhl, morit...@googlemail.com, syzkaller-o...@googlegroups.com
> #syz fix: Release PF und NET lock before calling copyout for

Your 'fix:' command is accepted, but please keep syzkaller-o...@googlegroups.com mailing list in CC next time. It serves as a history of what happened with each bug report. Thank you.

> DIOCIGETIFACES. OK sashan@ Reported-by:
> syzbot+b6afd1...@syzkaller.appspotmail.com
>
> Am Dienstag, 1. November 2022 schrieb syzbot <
> syzbot+444b02...@syzkaller.appspotmail.com>:

syzbot

unread,
Nov 21, 2022, 4:40:32 AM11/21/22
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Dec 5, 2022, 4:40:34 AM12/5/22
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Dec 19, 2022, 4:40:38 AM12/19/22
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Jan 2, 2023, 4:41:30 AM1/2/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com
This bug is marked as fixed by commit:
Release PF und NET lock before calling copyout for

But I can't find it in the tested trees[1] 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.

Kernel: OpenBSD
Dashboard link: https://syzkaller.appspot.com/bug?extid=444b020a92d87d6ded8b

---
[1] I expect the commit to be present in:

1. master branch of
https://github.com/openbsd/src.git

syzbot

unread,
Jan 16, 2023, 4:42:29 AM1/16/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Jan 30, 2023, 4:42:42 AM1/30/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Feb 13, 2023, 4:43:31 AM2/13/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Feb 27, 2023, 4:43:35 AM2/27/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Mar 13, 2023, 5:43:46 AM3/13/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Mar 27, 2023, 5:44:22 AM3/27/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Apr 10, 2023, 5:44:30 AM4/10/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Apr 24, 2023, 5:45:36 AM4/24/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
May 8, 2023, 5:46:32 AM5/8/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
May 22, 2023, 5:46:42 AM5/22/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Jun 5, 2023, 5:46:46 AM6/5/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Jun 19, 2023, 5:46:57 AM6/19/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Jul 3, 2023, 5:48:37 AM7/3/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Jul 17, 2023, 5:48:43 AM7/17/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Jul 31, 2023, 5:48:49 AM7/31/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Aug 14, 2023, 5:49:50 AM8/14/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Aug 28, 2023, 5:49:58 AM8/28/23
to morit...@googlemail.com, syzkaller-o...@googlegroups.com

Alexander Bluhm

unread,
Sep 3, 2023, 11:29:55 AM9/3/23
to syzbot, syzkaller-o...@googlegroups.com
#syz fix: Release PF und NET lock before calling copyout for DIOCIGETIFACES.

syzbot

unread,
Dec 2, 2023, 10:30:13 AM12/2/23
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com
This bug is marked as fixed by commit:
Release PF und NET lock before calling copyout for DIOCIGETIFACES.

syzbot

unread,
Dec 16, 2023, 10:30:16 AM12/16/23
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Dec 30, 2023, 10:31:12 AM12/30/23
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Jan 13, 2024, 10:31:15 AMJan 13
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Jan 27, 2024, 10:31:19 AMJan 27
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Feb 10, 2024, 10:32:19 AMFeb 10
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Feb 24, 2024, 10:33:11 AMFeb 24
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Mar 9, 2024, 10:33:18 AMMar 9
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Mar 23, 2024, 11:34:16 AMMar 23
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Apr 6, 2024, 11:35:21 AMApr 6
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
Apr 20, 2024, 11:36:14 AMApr 20
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com

syzbot

unread,
May 4, 2024, 11:36:18 AM (10 days ago) May 4
to alexand...@gmx.net, morit...@googlemail.com, syzkaller-o...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages