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.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,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 9E1A2C433B4 for ; Mon, 5 Apr 2021 03:04:27 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 119CD6128A for ; Mon, 5 Apr 2021 03:04:27 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 119CD6128A Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id A12206B0070; Sun, 4 Apr 2021 23:04:26 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 9C1E26B0075; Sun, 4 Apr 2021 23:04:26 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 862626B0078; Sun, 4 Apr 2021 23:04:26 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0239.hostedemail.com [216.40.44.239]) by kanga.kvack.org (Postfix) with ESMTP id 6AD436B0070 for ; Sun, 4 Apr 2021 23:04:26 -0400 (EDT) Received: from smtpin39.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id 2A25C80D8C00 for ; Mon, 5 Apr 2021 03:04:26 +0000 (UTC) X-FDA: 77996820132.39.B32FB69 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf21.hostedemail.com (Postfix) with ESMTP id 5FE47E0001B4 for ; Mon, 5 Apr 2021 03:04:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=cN/Spv35x0pwWsjEgNwu5WxmajnEowdx5QFLvVqU3nk=; b=NBUEnMuljaH7bseZP/nM/BXy4l dpVzSfQXkpoVGhvsoaYdbFLK0b/6Rg69PXgF+gcKYdhRI2SQjibmsjbjg58rzmq8doUsdofKBl6CH rDTxafMRBRMhhY6ZicRngICI/VUpR5bFGxVbYCjzUaQpTmHVum0bActiJ/dOjB1al2zuLvZcIKw0K C8JVSTVV35MhbmKpcmXi0njFVH7wYiCom+wOy6HsfxUxrDxFNWihZT/Dbq7DnqXjsqGFqGu4VQxtn qCFeKMX1EgIk+lQjp9RVy3w7IEJdZfD9onvWHYWlv66eJvIMMNUsEls05VyddAkG6DjmP8Oe2x+K6 BQLMBlBA==; Received: from willy by casper.infradead.org with local (Exim 4.94 #2 (Red Hat Linux)) id 1lTFX7-00ArAo-Bo; Mon, 05 Apr 2021 03:04:14 +0000 Date: Mon, 5 Apr 2021 04:04:09 +0100 From: Matthew Wilcox To: syzbot Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com Subject: Re: [syzbot] WARNING: suspicious RCU usage in remove_vma (2) Message-ID: <20210405030409.GE2531743@casper.infradead.org> References: <00000000000019114805bf0fb1bc@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00000000000019114805bf0fb1bc@google.com> X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: 5FE47E0001B4 X-Stat-Signature: 5kcqf8i157g9qqneciab73zg547gygmz Received-SPF: none (infradead.org>: No applicable sender policy available) receiver=imf21; identity=mailfrom; envelope-from=""; helo=casper.infradead.org; client-ip=90.155.50.34 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1617591864-230950 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: #syz dup: WARNING: suspicious RCU usage in getname_flags On Sat, Apr 03, 2021 at 04:23:20AM -0700, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: 1e43c377 Merge tag 'xtensa-20210329' of git://github.com/j.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=1052e1d6d00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=d1a3d65a48dbd1bc > dashboard link: https://syzkaller.appspot.com/bug?extid=26ad5e106ca477175819 > > 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+26ad5e106ca477175819@syzkaller.appspotmail.com > > ============================= > 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/29105. > > stack backtrace: > CPU: 0 PID: 29105 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+0x141/0x1d7 lib/dump_stack.c:120 > ___might_sleep+0x229/0x2c0 kernel/sched/core.c:8294 > remove_vma+0x44/0x170 mm/mmap.c:178 > exit_mmap+0x33f/0x590 mm/mmap.c:3229 > __mmput+0x122/0x470 kernel/fork.c:1090 > mmput+0x58/0x60 kernel/fork.c:1111 > exit_mm kernel/exit.c:501 [inline] > do_exit+0xb0a/0x2a60 kernel/exit.c:812 > do_group_exit+0x125/0x310 kernel/exit.c:922 > get_signal+0x47f/0x2150 kernel/signal.c:2781 > arch_do_signal_or_restart+0x2a8/0x1eb0 arch/x86/kernel/signal.c:789 > handle_signal_work kernel/entry/common.c:147 [inline] > exit_to_user_mode_loop kernel/entry/common.c:171 [inline] > exit_to_user_mode_prepare+0x148/0x250 kernel/entry/common.c:208 > __syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline] > syscall_exit_to_user_mode+0x19/0x60 kernel/entry/common.c:301 > entry_SYSCALL_64_after_hwframe+0x44/0xae > RIP: 0033:0x466459 > Code: Unable to access opcode bytes at RIP 0x46642f. > RSP: 002b:00007fdfaa117218 EFLAGS: 00000246 > ORIG_RAX: 00000000000000ca > RAX: 0000000000000000 RBX: 000000000056bf68 RCX: 0000000000466459 > RDX: 0000000000000000 RSI: 0000000000000080 RDI: 000000000056bf68 > RBP: 000000000056bf60 R08: 0000000000000000 R09: 0000000000000000 > R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf6c > R13: 00007fff64c569cf R14: 00007fdfaa117300 R15: 0000000000022000 > > > --- > 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. >