assert "part >= NUM && part < MAXPARTITIONS" failed in subr_disk.c

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 83ff66b05700 drm/amd/display: Set up pixel encoding for YC..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=12cbeb42580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=4637c9dac4f05fd880b0

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7e59272c764b/disk-83ff66b0.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/b976985515f2/bsd-83ff66b0.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8467acbdca5a/kernel-83ff66b0.xz

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

panic: kernel diagnostic assertion "part >= 0 && part < MAXPARTITIONS" failed: file "/syzkaller/managers/multicore/kernel/sys/kern/subr_disk.c", line 1169
Starting stack trace...
panic(ffffffff833a13e1) at panic+0x1d0 sys/kern/subr_prf.c:229
__assert(ffffffff833de65a,ffffffff833bbce4,491,ffffffff833cf36a) at __assert+0x29 sys/kern/subr_prf.c:-1
disk_openpart(ffff8000001a1048,1a,2000,1) at disk_openpart+0x20d
sdopen(d1a,101,2000,ffff8000fffe8fb0) at sdopen+0x261 sys/scsi/sd.c:429
spec_open(ffff80003c4be6a8) at spec_open+0x2d9 sys/kern/spec_vnops.c:150
VOP_OPEN(fffffd8063ee15f8,101,fffffd80097fd4e0,ffff8000fffe8fb0) at VOP_OPEN+0x8b sys/kern/vfs_vops.c:138
vn_open(ffff80003c4be8f0,101,0) at vn_open+0x6a0 sys/kern/vfs_vnops.c:177
doopenat(ffff8000fffe8fb0,ffffff9c,2000000004c0,100,0,ffff80003c4beaa0) at doopenat+0x35b sys/kern/vfs_syscalls.c:1138
syscall(ffff80003c4beb50) at syscall+0xbd4 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff80003c4beb50) at syscall+0xbd4 sys/arch/amd64/amd64/trap.c:765
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x1b8a0a32f20, count: 247
End of stack trace.


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[Greg Steuck]

#syz fix: bogus asserts; ok krw gnezdo

--
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 visit https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/6916afb0.a70a0220.3124cb.0045.GAE%40google.com.