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_DIGITS, FROM_LOCAL_HEX,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 C8CA9C433ED for ; Sun, 4 Apr 2021 15:15:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9D11661365 for ; Sun, 4 Apr 2021 15:15:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230369AbhDDPPX (ORCPT ); Sun, 4 Apr 2021 11:15:23 -0400 Received: from mail-io1-f70.google.com ([209.85.166.70]:52516 "EHLO mail-io1-f70.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229861AbhDDPPT (ORCPT ); Sun, 4 Apr 2021 11:15:19 -0400 Received: by mail-io1-f70.google.com with SMTP id d4so9528767iop.19 for ; Sun, 04 Apr 2021 08:15:13 -0700 (PDT) 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=dxD0Hg0qysVOsDo3bqgEGmetC7jdDlc6pL/RNn78V90=; b=qZ632KS0PifrMCi8IebZx8XH0DsFFbhMH2AxJRVlml7fhdiN8KzE9naZA6b1W+tw4t q2ccaZ7L6TYoNcrGvgvjfwnfYwUXE1Nixis37qITDI6foA/5sHEPliIAX35PVRQ24mtI 9+tndG2FAXi8YEazdVO3BHIDADaLpXjs4ZQoPbYvkswaWaDp07Ow3tKga3/nRDp+YdVI WGsOMzyy+neiT33Ie/KMBvuKG8QnSs+vtvll+xz2oBAqvWEdqmK7I9ZHkZ2BJopegCOH 2fIgvEOC7ZiGGq1xGzq9RjVHTu8wajkozwftqcJ2cOuLMmp76Gcgt33aYJbHhC1nziqh YZWg== X-Gm-Message-State: AOAM531rNpLwb+CcSnKPB5BdZU/bUYpElu5r1KvrLb/6qvgE52M3OVp2 4gWvgniTGL0yrImP18TNIASBXVFE/O1GIpoDeFAR16M/Kobv X-Google-Smtp-Source: ABdhPJzVQjsJDUibxgnfqxPohifHOtt7o3aW3XOo1HD1pnjGDI9XFknYFRBJTAwNYD8USisEec6RGddqZ2Y4Cla2IahmipYMa8yY MIME-Version: 1.0 X-Received: by 2002:a92:7b05:: with SMTP id w5mr16393092ilc.232.1617549313028; Sun, 04 Apr 2021 08:15:13 -0700 (PDT) Date: Sun, 04 Apr 2021 08:15:13 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000035b58705bf270c19@google.com> Subject: [syzbot] WARNING: suspicious RCU usage in list_lru_destroy 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: 5e46d1b7 reiserfs: update reiserfs_xattrs_initialized() co.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15556cced00000 kernel config: https://syzkaller.appspot.com/x/.config?x=71a75beb62b62a34 dashboard link: https://syzkaller.appspot.com/bug?extid=d7dd989878658902c6d6 compiler: Debian clang version 11.0.1-2 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+d7dd989878658902c6d6@syzkaller.appspotmail.com EXT4-fs (loop0): mount failed ============================= WARNING: suspicious RCU usage 5.12.0-rc5-syzkaller #0 Not tainted ----------------------------- kernel/sched/core.c:8294 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 syz-executor.0/10672. stack backtrace: CPU: 0 PID: 10672 Comm: syz-executor.0 Not tainted 5.12.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:79 [inline] dump_stack+0x176/0x24e lib/dump_stack.c:120 ___might_sleep+0x6e/0x530 kernel/sched/core.c:8294 down_read+0x17/0x50 kernel/locking/rwsem.c:1352 list_lru_destroy+0x49/0x390 mm/list_lru.c:628 deactivate_locked_super+0xbf/0xf0 fs/super.c:343 mount_bdev+0x288/0x3a0 fs/super.c:1369 legacy_get_tree+0xea/0x180 fs/fs_context.c:592 vfs_get_tree+0x86/0x270 fs/super.c:1497 do_new_mount fs/namespace.c:2903 [inline] path_mount+0x188a/0x29a0 fs/namespace.c:3233 do_mount fs/namespace.c:3246 [inline] __do_sys_mount fs/namespace.c:3454 [inline] __se_sys_mount+0x28c/0x320 fs/namespace.c:3431 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x46797a Code: 48 c7 c2 bc ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f77bde01fa8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 000000000046797a RDX: 0000000020000300 RSI: 0000000020000100 RDI: 00007f77bde02000 RBP: 00007f77bde02040 R08: 00007f77bde02040 R09: 0000000020000300 R10: 0000000000000000 R11: 0000000000000206 R12: 0000000020000300 R13: 0000000020000100 R14: 00007f77bde02000 R15: 00000000200000c0 --- 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.