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=unavailable 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 C393BC2BBCD for ; Wed, 16 Dec 2020 19:34:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6FD66223E8 for ; Wed, 16 Dec 2020 19:34:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388832AbgLPTev (ORCPT ); Wed, 16 Dec 2020 14:34:51 -0500 Received: from mail-io1-f71.google.com ([209.85.166.71]:35331 "EHLO mail-io1-f71.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388261AbgLPTev (ORCPT ); Wed, 16 Dec 2020 14:34:51 -0500 Received: by mail-io1-f71.google.com with SMTP id a1so14390067ios.2 for ; Wed, 16 Dec 2020 11:34:35 -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=ecTUXuxQnoSm8RKPxvl0tmvMSXXjeO+92fr5WrQIzzM=; b=g0msGMzZaTyxHo7ips2lW8zpJjw8D6mqpCHlwqeQD+UXymhSs+4y63urKaELSxB1mw Km/WNgebXYs3PeZtaDkz1fZpwItmUkDF56SVNcmuTz0sFk5sc2qyzp4LhowquBngZxKa Yoa55KUf2TfEAz0k+V3VxpyCU8YktbsTP+PfzPPLr10Eo6OumK5h+MjcCvTYMhUwg8Tc D7K8S03cRlorOBuCpLAsmgL6UUuwJAXcmgTFWd+jgXE+5VbDBnxX+cf/smC7KNbEXVoa kYcJ+ro41FlJtW7gc/hxMzQ0qKlwQN08Y+g1zyACGuvPax5BHuh5Cuj+yY16mxfqBHIT b1wg== X-Gm-Message-State: AOAM531ZELYSkHdMsNkQ4YZI9aUoFtD8NCjD02oB37BWOY9fLTMQYuNd eMXL6M4yLH4iJkHbgRTSATkOKwBsNzckXDZ4ph5JSYW2wmsQ X-Google-Smtp-Source: ABdhPJyigXczjaGdO4uSdKTU+0X5gilBVE4f3h4pJpYB7atKcLS89UMO3NHcL6d7en2a+VTIb+IODPb+UcP0JWKa+oDQcmgwj5sD MIME-Version: 1.0 X-Received: by 2002:a6b:b8d6:: with SMTP id i205mr42768676iof.135.1608147250209; Wed, 16 Dec 2020 11:34:10 -0800 (PST) Date: Wed, 16 Dec 2020 11:34:10 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000009867cb05b699f5b6@google.com> Subject: WARNING: suspicious RCU usage in count From: syzbot To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 7f376f19 Merge tag 'mtd/fixes-for-5.10-rc8' of git://git.k.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1217bb7f500000 kernel config: https://syzkaller.appspot.com/x/.config?x=ee8a1012a5314210 dashboard link: https://syzkaller.appspot.com/bug?extid=51ce7a5794c3b12a70d1 compiler: gcc (GCC) 10.1.0-syz 20200507 userspace arch: i386 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+51ce7a5794c3b12a70d1@syzkaller.appspotmail.com ============================= WARNING: suspicious RCU usage 5.10.0-rc7-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 udevd/9038. stack backtrace: CPU: 3 PID: 9038 Comm: udevd Not tainted 5.10.0-rc7-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 count.constprop.0+0x164/0x270 fs/exec.c:449 do_execveat_common+0x2fd/0x7c0 fs/exec.c:1893 do_execve fs/exec.c:1983 [inline] __do_sys_execve fs/exec.c:2059 [inline] __se_sys_execve fs/exec.c:2054 [inline] __x64_sys_execve+0x8f/0xc0 fs/exec.c:2054 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fbc6f64c207 Code: 77 19 f4 48 89 d7 44 89 c0 0f 05 48 3d 00 f0 ff ff 76 e0 f7 d8 64 41 89 01 eb d8 f7 d8 64 41 89 01 eb df b8 3b 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 02 f3 c3 48 8b 15 00 8c 2d 00 f7 d8 64 89 02 RSP: 002b:00007ffcfe4966d8 EFLAGS: 00000206 ORIG_RAX: 000000000000003b RAX: ffffffffffffffda RBX: 00000000ffffffff RCX: 00007fbc6f64c207 RDX: 0000000000f1dfd0 RSI: 00007ffcfe4967d0 RDI: 00007ffcfe4977e0 RBP: 0000000000625500 R08: 00000000000022fb R09: 00000000000022fb R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000f1dfd0 R13: 0000000000000007 R14: 0000000000f0e250 R15: 0000000000000005 --- 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.