From: syzbot <syzbot+e74b94fe601ab9552d69@syzkaller.appspotmail.com>
To: bristot@redhat.com, bsegall@google.com, dietmar.eggemann@arm.com,
juri.lelli@redhat.com, linux-kernel@vger.kernel.org,
mgorman@suse.de, mingo@redhat.com, peterz@infradead.org,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com,
vincent.guittot@linaro.org
Subject: [syzbot] BUG: unable to handle kernel access to user memory in schedule_tail
Date: Wed, 10 Mar 2021 08:46:14 -0800 [thread overview]
Message-ID: <000000000000b74f1b05bd316729@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 0d7588ab riscv: process: Fix no prototype for arch_dup_tas..
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=1212c6e6d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e3c595255fb2d136
dashboard link: https://syzkaller.appspot.com/bug?extid=e74b94fe601ab9552d69
userspace arch: riscv64
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+e74b94fe601ab9552d69@syzkaller.appspotmail.com
Unable to handle kernel access to user memory without uaccess routines at virtual address 000000002749f0d0
Oops [#1]
Modules linked in:
CPU: 1 PID: 4875 Comm: syz-executor.0 Not tainted 5.12.0-rc2-syzkaller-00467-g0d7588ab9ef9 #0
Hardware name: riscv-virtio,qemu (DT)
epc : schedule_tail+0x72/0xb2 kernel/sched/core.c:4264
ra : task_pid_vnr include/linux/sched.h:1421 [inline]
ra : schedule_tail+0x70/0xb2 kernel/sched/core.c:4264
epc : ffffffe00008c8b0 ra : ffffffe00008c8ae sp : ffffffe025d17ec0
gp : ffffffe005d25378 tp : ffffffe00f0d0000 t0 : 0000000000000000
t1 : 0000000000000001 t2 : 00000000000f4240 s0 : ffffffe025d17ee0
s1 : 000000002749f0d0 a0 : 000000000000002a a1 : 0000000000000003
a2 : 1ffffffc0cfac500 a3 : ffffffe0000c80cc a4 : 5ae9db91c19bbe00
a5 : 0000000000000000 a6 : 0000000000f00000 a7 : ffffffe000082eba
s2 : 0000000000040000 s3 : ffffffe00eef96c0 s4 : ffffffe022c77fe0
s5 : 0000000000004000 s6 : ffffffe067d74e00 s7 : ffffffe067d74850
s8 : ffffffe067d73e18 s9 : ffffffe067d74e00 s10: ffffffe00eef96e8
s11: 000000ae6cdf8368 t3 : 5ae9db91c19bbe00 t4 : ffffffc4043cafb2
t5 : ffffffc4043cafba t6 : 0000000000040000
status: 0000000000000120 badaddr: 000000002749f0d0 cause: 000000000000000f
Call Trace:
[<ffffffe00008c8b0>] schedule_tail+0x72/0xb2 kernel/sched/core.c:4264
[<ffffffe000005570>] ret_from_exception+0x0/0x14
Dumping ftrace buffer:
(ftrace buffer empty)
---[ end trace b5f8f9231dc87dda ]---
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2021-03-10 16:46 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 16:46 syzbot [this message]
2021-03-10 17:16 ` [syzbot] BUG: unable to handle kernel access to user memory in schedule_tail Dmitry Vyukov
2021-03-10 17:16 ` Dmitry Vyukov
2021-03-10 22:24 ` Ben Dooks
2021-03-10 22:24 ` Ben Dooks
2021-03-11 6:39 ` Alex Ghiti
2021-03-11 6:39 ` Alex Ghiti
2021-03-11 6:50 ` Dmitry Vyukov
2021-03-11 6:50 ` Dmitry Vyukov
2021-03-11 6:52 ` Dmitry Vyukov
2021-03-11 6:52 ` Dmitry Vyukov
2021-03-11 10:41 ` Ben Dooks
2021-03-11 10:41 ` Ben Dooks
2021-03-12 13:49 ` Ben Dooks
2021-03-12 13:49 ` Ben Dooks
2021-03-12 15:12 ` Dmitry Vyukov
2021-03-12 15:12 ` Dmitry Vyukov
2021-03-12 16:25 ` Alex Ghiti
2021-03-12 16:25 ` Alex Ghiti
2021-03-12 20:12 ` Ben Dooks
2021-03-12 20:12 ` Ben Dooks
2021-03-13 7:20 ` Dmitry Vyukov
2021-03-13 7:20 ` Dmitry Vyukov
2021-03-15 16:55 ` Ben Dooks
2021-03-15 16:55 ` Ben Dooks
2021-03-18 14:34 ` Dmitry Vyukov
2021-03-18 14:34 ` Dmitry Vyukov
2021-03-15 21:38 ` Ben Dooks
2021-03-15 21:38 ` Ben Dooks
2021-03-16 8:52 ` Dmitry Vyukov
2021-03-16 8:52 ` Dmitry Vyukov
2021-03-16 11:35 ` Ben Dooks
2021-03-16 11:35 ` Ben Dooks
2021-03-16 11:44 ` Dmitry Vyukov
2021-03-16 11:44 ` Dmitry Vyukov
2021-03-12 16:30 ` Ben Dooks
2021-03-12 16:30 ` Ben Dooks
2021-03-12 16:34 ` Ben Dooks
2021-03-12 16:34 ` Ben Dooks
2021-03-12 16:36 ` Ben Dooks
2021-03-12 16:36 ` Ben Dooks
2021-03-12 17:34 ` Dmitry Vyukov
2021-03-12 17:34 ` Dmitry Vyukov
2021-03-12 17:38 ` Dmitry Vyukov
2021-03-12 17:38 ` Dmitry Vyukov
2021-03-18 9:41 ` Ben Dooks
2021-03-18 9:41 ` Ben Dooks
2021-03-18 10:05 ` Dmitry Vyukov
2021-03-18 10:05 ` Dmitry Vyukov
2021-03-18 12:52 ` Ben Dooks
2021-03-18 12:52 ` Ben Dooks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000b74f1b05bd316729@google.com \
--to=syzbot+e74b94fe601ab9552d69@syzkaller.appspotmail.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vincent.guittot@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.