Are you seeing this error or a different one ? I used the
syzkaller_defconfig from the patch below on v5.18.
https://lore.kernel.org/all/2022041917495...@rivosinc.com/
[ 15.076116][ T1] Mandatory Access Control activated.
[ 15.158241][ T1] AppArmor: AppArmor Filesystem Enabled
[ 16.150870][ T1] NET: Registered PF_INET protocol family
[ 16.166167][ T1] IP idents hash table entries: 32768 (order: 6,
262144 bytes, linear)
[ 16.188727][ T1] Unable to handle kernel paging request at
virtual address ffebfffeffff2000
[ 16.192727][ T1] Oops [#1]
[ 16.193479][ T1] Modules linked in:
[ 16.194687][ T1] CPU: 3 PID: 1 Comm: swapper/0 Not tainted
5.18.0-00001-g37ac279268bf-dirty #9
[ 16.196486][ T1] Hardware name: riscv-virtio,qemu (DT)
[ 16.197836][ T1] epc : kasan_check_range+0x9e/0x14e
[ 16.199104][ T1] ra : memset+0x1e/0x4c
[ 16.200091][ T1] epc : ffffffff804787e0 ra : ffffffff80478f30 sp
: ff600000073ffb70
[ 16.201420][ T1] gp : ffffffff85879e80 tp : ff600000073f0000 t0
: 7300000000000000
[ 16.202762][ T1] t1 : ffebfffeffff21ff t2 : 73746e6564692050 s0
: ff600000073ffba0
[ 16.204047][ T1] s1 : 0000000000001000 a0 : ffebfffeffff2200 a1
: 0000000000001000
[ 16.205312][ T1] a2 : 0000000000000001 a3 : ffffffff803a4f32 a4
: ff5ffffffff90000
[ 16.206592][ T1] a5 : ffebfffeffff2000 a6 : 0000004000000000 a7
: ff5ffffffff90fff
[ 16.207865][ T1] s2 : ff5ffffffff90000 s3 : 0000000000000000 s4
: ffffffff8467ea90
[ 16.209134][ T1] s5 : 0000000000000000 s6 : ff5ffffffff90000 s7
: 0000000000000000
[ 16.210394][ T1] s8 : 0000000000001000 s9 : ffffffff8587ca40
s10: 0000000000000004
[ 16.211952][ T1] s11: ffffffff858a03a0 t3 : 0000000000000000 t4
: 0000000000000040
[ 16.213469][ T1] t5 : ffebfffeffff2200 t6 : ff600000073ff738
[ 16.214853][ T1] status: 0000000200000120 badaddr:
ffebfffeffff2000 cause: 000000000000000d
[ 16.216910][ T1] Call Trace:
[ 16.217816][ T1] [<ffffffff803a4f32>] pcpu_alloc+0x844/0x1254
[ 16.219110][ T1] [<ffffffff803a59a0>] __alloc_percpu+0x28/0x34
[ 16.220244][ T1] [<ffffffff8328824a>] ip_rt_init+0x17e/0x382
[ 16.221606][ T1] [<ffffffff8328861c>] ip_init+0x18/0x30
[ 16.222719][ T1] [<ffffffff8328a0ee>] inet_init+0x2a6/0x550
[ 16.223863][ T1] [<ffffffff80003204>] do_one_initcall+0x130/0x7dc
[ 16.225002][ T1] [<ffffffff83201fbc>] kernel_init_freeable+0x510/0x5b4
[ 16.226273][ T1] [<ffffffff8319842a>] kernel_init+0x28/0x21c
[ 16.227337][ T1] [<ffffffff80005818>] ret_from_exception+0x0/0x10
[ 16.229910][ T1] ---[ end trace 0000000000000000 ]---
[ 16.231880][ T1] Kernel panic - not syncing: Fatal exception
> Thanks,
>
> Alex
>
>
> >
> >> However, as you'll see in the cover letter, I have an issue with
> >> another KASAN config and if you can take a look at the stacktrace and
> >> see if that rings a bell, that would be great.
> >>
> >> Don't hesitate next time to ping me when the riscv syzbot instance fails :)
> >>
> >> Alex
> >>
> >>
> >>> --
> >>> Best Regards,
> >>> Aleksandr
> >>>
> >>>> Thanks again,
> >>>>
> >>>> Alex
> >> --
> >> You received this message because you are subscribed to the Google Groups "kasan-dev" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an email to
kasan-dev+...@googlegroups.com.
> >> To view this discussion on the web visit
https://groups.google.com/d/msgid/kasan-dev/CA%2BzEjCtB0rTuNAJkrM2q3JQL7D-9fAXBo0Ud0w__gy9CAfo_Ag%40mail.gmail.com.
>
Regards,
Atish