kernel panic: corrupted stack end in inet6_ioctl

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0966d385830d riscv: Fix auipc+jalr relocation range checks
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=15a367e5880000
kernel config: https://syzkaller.appspot.com/x/.config?x=6295d67591064921
dashboard link: https://syzkaller.appspot.com/bug?extid=06e0b7230fefced48e10
compiler: riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: riscv64
CC: [b...@vger.kernel.org da...@davemloft.net dsa...@kernel.org edum...@google.com ku...@kernel.org linux-...@vger.kernel.org net...@vger.kernel.org pab...@redhat.com yosh...@linux-ipv6.org]

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+06e0b7...@syzkaller.appspotmail.com

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 6083 Comm: syz-executor.0 Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[<ffffffff8000a228>] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:113
[<ffffffff831668cc>] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:119
[<ffffffff831756ba>] __dump_stack lib/dump_stack.c:88 [inline]
[<ffffffff831756ba>] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:106
[<ffffffff83175742>] dump_stack+0x1c/0x24 lib/dump_stack.c:113
[<ffffffff83166fa8>] panic+0x24a/0x634 kernel/panic.c:233
[<ffffffff831a688a>] schedule_debug kernel/sched/core.c:5541 [inline]
[<ffffffff831a688a>] schedule+0x0/0x14c kernel/sched/core.c:6187
[<ffffffff831a6b00>] preempt_schedule_common+0x4e/0xde kernel/sched/core.c:6462
[<ffffffff831a6bc4>] preempt_schedule+0x34/0x36 kernel/sched/core.c:6487
[<ffffffff8046ef56>] __slab_alloc.constprop.0+0x8a/0x8c mm/slub.c:3107
[<ffffffff804705ec>] slab_alloc_node mm/slub.c:3196 [inline]
[<ffffffff804705ec>] slab_alloc mm/slub.c:3238 [inline]
[<ffffffff804705ec>] kmem_cache_alloc_trace+0x2a2/0x2e0 mm/slub.c:3255
[<ffffffff80c00e38>] kmalloc include/linux/slab.h:581 [inline]
[<ffffffff80c00e38>] kzalloc include/linux/slab.h:715 [inline]
[<ffffffff80c00e38>] ref_tracker_alloc+0x10c/0x33e lib/ref_tracker.c:77
[<ffffffff82d6ed44>] netdev_tracker_alloc include/linux/netdevice.h:3859 [inline]
[<ffffffff82d6ed44>] fib6_nh_init+0x3bc/0x10c0 net/ipv6/route.c:3631
[<ffffffff82d705b8>] ip6_route_info_create+0xb70/0xf78 net/ipv6/route.c:3809
[<ffffffff82d70c66>] ip6_route_add+0x2a/0x148 net/ipv6/route.c:3853
[<ffffffff82d3591c>] addrconf_add_mroute+0x1d4/0x302 net/ipv6/addrconf.c:2488
[<ffffffff82d3f69e>] addrconf_add_dev+0x102/0x156 net/ipv6/addrconf.c:2506
[<ffffffff82d4697e>] inet6_addr_add+0x140/0x646 net/ipv6/addrconf.c:2922
[<ffffffff82d4d0f6>] addrconf_add_ifaddr+0x142/0x1a6 net/ipv6/addrconf.c:3050
[<ffffffff82d16018>] inet6_ioctl+0xf2/0x20c net/ipv6/af_inet6.c:569
[<ffffffff826d51d4>] sock_do_ioctl net/socket.c:1122 [inline]
[<ffffffff826d51d4>] sock_ioctl+0x2ac/0x68c net/socket.c:1239
[<ffffffff804f6ff8>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff804f6ff8>] __do_sys_ioctl fs/ioctl.c:874 [inline]
[<ffffffff804f6ff8>] sys_ioctl+0x75c/0x139e fs/ioctl.c:860
[<ffffffff80005716>] ret_from_syscall+0x0/0x2
SMP: stopping secondary CPUs
Rebooting in 86400 seconds..


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

[Dmitry Vyukov]

#syz fix: riscv: Increase stack size under KASAN

> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/0000000000002c535a05ee48b190%40google.com.