From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C97C9C433DB for ; Wed, 10 Mar 2021 16:46:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A53AD64FC3 for ; Wed, 10 Mar 2021 16:46:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232470AbhCJQqS (ORCPT ); Wed, 10 Mar 2021 11:46:18 -0500 Received: from mail-il1-f198.google.com ([209.85.166.198]:42186 "EHLO mail-il1-f198.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233430AbhCJQqP (ORCPT ); Wed, 10 Mar 2021 11:46:15 -0500 Received: by mail-il1-f198.google.com with SMTP id r16so3735265ilj.9 for ; Wed, 10 Mar 2021 08:46:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=dNbHlhYE0Ak8ywIpAqhidmfhEn8ab4ogc1vEklKjLuM=; b=F5E1/DbXHft0OUe9JIOUWK65Y+NWA3lxJGdx2gW9GuSebK5TjZ4umkk2qqxN+BKX5s TLw9ug52wG8Cs5z+s1R+2KnuHDczWLLRYFoFScrcVeEu4ZjcrqmxSSxU5bxFKVYXk6tX QwWjELir0d/BViah3PCBxbE3UavAk2h6ZrvoRizS/9JwK/sOBDsOI5MUostAL/V4DlbW luxntar6MS2dPt/Xy05j+GMk9XuuIm2DMILrYCXdQviaXFphRnxXzspUsI+79lCrYzwd oVInMg93mAx5/hsP/xBP+H9AAWGuabYP5GcPSLLjRFRTMK1Rl0Hp/d0Y4/O4jOYV88BI Tv7g== X-Gm-Message-State: AOAM5318v/06bf8vlYZjGlNH9mmNRqW4qLfQAPpwvfP5/JcF85fAtcLE wfs1agCaRCupw8aZBzc0zaH7TjNBweXg56i7udezKuUWW03v X-Google-Smtp-Source: ABdhPJymHOWc4pLU0FSoQbxfy2ZT1aZKoOzMVB28ICyPIyCBFxw4XVVUX471flMJABnJjFck+/2YFHiOxzk8FAUMVh9ekwUiiFdb MIME-Version: 1.0 X-Received: by 2002:a02:c8d4:: with SMTP id q20mr3743659jao.90.1615394774664; Wed, 10 Mar 2021 08:46:14 -0800 (PST) Date: Wed, 10 Mar 2021 08:46:14 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000b74f1b05bd316729@google.com> Subject: [syzbot] BUG: unable to handle kernel access to user memory in schedule_tail From: syzbot 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 Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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: [] schedule_tail+0x72/0xb2 kernel/sched/core.c:4264 [] 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.