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=-3.7 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no 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 9FD56C83012 for ; Tue, 1 Dec 2020 09:21:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6B829206CA for ; Tue, 1 Dec 2020 09:21:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390493AbgLAJVK (ORCPT ); Tue, 1 Dec 2020 04:21:10 -0500 Received: from mail-il1-f199.google.com ([209.85.166.199]:35626 "EHLO mail-il1-f199.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389319AbgLAJVE (ORCPT ); Tue, 1 Dec 2020 04:21:04 -0500 Received: by mail-il1-f199.google.com with SMTP id l2so939062ilj.2 for ; Tue, 01 Dec 2020 01:20:44 -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=CvrpfhVkHKuVC9Iwh6IlCX5MJUoOFtMuO60G4zzaPDo=; b=GngFH4HocG1qAKhV7zHgB/dOwcQxGYY9nEoLZQG/zsMAQ3cgx1KDFB3UJ0HnvYRIdH Y05GzkEDWEA9mxlsz5AcP79HBp867DNIt0ACLfRTmQc6F88NDt9TR9SSrhRtS+DU2uiD YYS0wfEarozWmfdKdE1cy6s1A4w2z0Fu5/R7uMsbZLUjHu72OodhdeUQ7JKgHBREZGJt X3SVdSekc4O3ryQmk+aGBbkEINUSUy4hMFwhCAsoS7h5yj5KV1U1JaM8bdA7R2l5aC1a 15hSrypFE3VgCOvCL362COe81as9xVkgCpaV15704Dwk4/KJ6+M8YmoAi0+K+dDw6Wpn W7gw== X-Gm-Message-State: AOAM530wsAS5/p+hExilSaOF4Ku2eXvpbl5L2Iu3AhRI6Q2m1hm3Uglj X/v8jXD8laykHD9A3tjeQm3wjDeYbcnsrOa4qFs1KnYVYYFO X-Google-Smtp-Source: ABdhPJw5WC9aVX5e6jJPwQTAq3prgI208vQqNeitL0Pd4Zy1ch4A07HtA1fM9GTFxeLTi9PPtL3x9KYAYS10hcz3vRwUkVaRKEIM MIME-Version: 1.0 X-Received: by 2002:a6b:5911:: with SMTP id n17mr1685480iob.34.1606814418659; Tue, 01 Dec 2020 01:20:18 -0800 (PST) Date: Tue, 01 Dec 2020 01:20:18 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000a4ef2405b563a244@google.com> Subject: WARNING: suspicious RCU usage in remove_vma From: syzbot To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com 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: 99c710c4 Merge tag 'platform-drivers-x86-v5.10-2' of git:/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15638bf1500000 kernel config: https://syzkaller.appspot.com/x/.config?x=6d1e98d0b97781e4 dashboard link: https://syzkaller.appspot.com/bug?extid=a6beff5dda6d8ea00582 compiler: gcc (GCC) 10.1.0-syz 20200507 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+a6beff5dda6d8ea00582@syzkaller.appspotmail.com ============================= WARNING: suspicious RCU usage 5.10.0-rc5-syzkaller #0 Not tainted ----------------------------- kernel/sched/core.c:7270 Illegal context switch in RCU-bh read-side critical section! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 0 no locks held by blkid/11233. stack backtrace: CPU: 1 PID: 11233 Comm: blkid Not tainted 5.10.0-rc5-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x107/0x163 lib/dump_stack.c:118 ___might_sleep+0x220/0x2b0 kernel/sched/core.c:7270 remove_vma+0x44/0x170 mm/mmap.c:178 exit_mmap+0x351/0x530 mm/mmap.c:3233 __mmput+0x122/0x470 kernel/fork.c:1079 mmput+0x53/0x60 kernel/fork.c:1100 exit_mm kernel/exit.c:486 [inline] do_exit+0xa72/0x29b0 kernel/exit.c:796 do_group_exit+0x125/0x310 kernel/exit.c:906 __do_sys_exit_group kernel/exit.c:917 [inline] __se_sys_exit_group kernel/exit.c:915 [inline] __x64_sys_exit_group+0x3a/0x50 kernel/exit.c:915 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f2b794631e8 Code: Unable to access opcode bytes at RIP 0x7f2b794631be. RSP: 002b:00007ffcfbbb2458 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f2b794631e8 RDX: 0000000000000002 RSI: 000000000000003c RDI: 0000000000000002 RBP: 00007f2b79738840 R08: 00000000000000e7 R09: ffffffffffffffa8 R10: 00007f2b7973e740 R11: 0000000000000246 R12: 00007f2b79738840 R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000000 --- 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.