Hello,
syzbot found the following issue on:
HEAD commit: 9dd3114fe566 Revert "Fix checkalias contract to register t..
git tree:
https://github.com/blackgnezdo/openbsd-src.git syzbot-kasan
console output:
https://syzkaller.appspot.com/x/log.txt?x=17a33011580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=85e25e37d09e1b88
dashboard link:
https://syzkaller.appspot.com/bug?extid=7305f7ff75d94d60eae5
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/b3a0da640b5d/disk-9dd3114f.raw.xz
bsd.gdb:
https://storage.googleapis.com/syzbot-assets/823e2c016fd0/bsd-9dd3114f.gdb.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/29acf01f0052/kernel-9dd3114f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+7305f7...@syzkaller.appspotmail.com
KASAN: invalid read of 4 bytes at 0xffffffff850db034 from pc 0xffffffff83d58cec
KASAN: first bad byte at 0xffffffff850db034 (+0); shadow 0xfa: global redzone (out-of-bounds)
KASAN: 0xffffffff850db034 is 1428 bytes to the right of the 8160-byte global 'cdevsw' (/syzkaller/managers/kasan/kernel/sys/arch/amd64/amd64/conf.c)
KASAN: pc: checkalias+0x64c
KASAN: call trace:
#0 __asan_load4_noabort+0x82 kasan_shadow_check sys/kern/subr_kasan.c:1014 [inline]
#0 __asan_load4_noabort+0x82 sys/kern/subr_kasan.c:1098
#1 checkalias+0x64c sys/kern/vfs_subr.c:608
#2 ffs_vinit+0x240 sys/ufs/ffs/ffs_subr.c:-1
#3 ffs_vget+0x7b4 sys/ufs/ffs/ffs_vfsops.c:1285
#4 ufs_lookup+0x174e sys/ufs/ufs/ufs_lookup.c:478
#5 VOP_LOOKUP+0xea sys/kern/vfs_vops.c:85
#6 vfs_lookup+0xe55 sys/kern/vfs_lookup.c:585
#7 namei+0xcba sys/kern/vfs_lookup.c:250
#8 dounlinkat+0x15c sys/kern/vfs_syscalls.c:1807
#9 syscall+0x118e mi_syscall sys/sys/syscall_mi.h:176 [inline]
#9 syscall+0x118e sys/arch/amd64/amd64/trap.c:791
#10 Xsyscall+0x128
KASAN: shadow of 0xffffffff850daf00..0xffffffff850db180 (1 cell = 8 bytes):
0xffffffff850daf00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0xffffffff850daf80: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
>0xffffffff850db000: fa fa fa fa fa fa[fa]fa fa fa fa fa fa fa fa fa
0xffffffff850db080: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0xffffffff850db100: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
KASAN: legend: 00 valid; 01..07 partial; fb malloc redzone; fc malloc freed; fd pool freed; fe kmem; fa global; f1..f4/f8 stack/scope
panic: Caught invalid memory access at ffffffff850db034 size 4 op 0
Stopped at db_enter+0x17: popq %rbp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*262879 50331 0 0 0x4000000 0K syz-executor
db_enter() at db_enter+0x17 sys/arch/amd64/amd64/db_interface.c:457
panic(ffffffff847b9457) at panic+0x296 sys/kern/subr_prf.c:198
__asan_load4_noabort(ffffffff850db034) at __asan_load4_noabort+0xa3
checkalias(ffff800001952e98,776b,ffff800000de5000) at checkalias+0x64c sys/kern/vfs_subr.c:608
ffs_vinit(ffff800000de5000,ffff8000396c9f00) at ffs_vinit+0x240 sys/ufs/ffs/ffs_subr.c:-1
ffs_vget(ffff800000de5000,69f3,ffff8000396ca100) at ffs_vget+0x7b4 sys/ufs/ffs/ffs_vfsops.c:1285
ufs_lookup() at ufs_lookup+0x174e sys/ufs/ufs/ufs_lookup.c:478
VOP_LOOKUP(ffff800001d26548,ffff8000396ca670,ffff8000396ca6a0) at VOP_LOOKUP+0xea sys/kern/vfs_vops.c:85
vfs_lookup(ffff8000396ca640) at vfs_lookup+0xe55 sys/kern/vfs_lookup.c:585
namei(ffff8000396ca640) at namei+0xcba sys/kern/vfs_lookup.c:250
dounlinkat(ffff800035ea5cb8,ffffff9c,200000000040,0) at dounlinkat+0x15c sys/kern/vfs_syscalls.c:1807
syscall(ffff8000396ca930) at syscall+0x118e mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff8000396ca930) at syscall+0x118e sys/arch/amd64/amd64/trap.c:791
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x9a926e0260, count: 2
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports. Insufficient info makes it difficult to find and fix bugs.
ddb{0}>
ddb{0}> set $lines = 0
ddb{0}>
---
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