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 DA0F7C433E0 for ; Wed, 20 Jan 2021 04:05:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8BDAF23121 for ; Wed, 20 Jan 2021 04:05:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731573AbhATEFG (ORCPT ); Tue, 19 Jan 2021 23:05:06 -0500 Received: from mail-io1-f72.google.com ([209.85.166.72]:55369 "EHLO mail-io1-f72.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730009AbhATEAG (ORCPT ); Tue, 19 Jan 2021 23:00:06 -0500 Received: by mail-io1-f72.google.com with SMTP id j25so39566158iog.22 for ; Tue, 19 Jan 2021 19:59:50 -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=pveP83Yk7K0d5WBq+35hC0CXs3D/scBCKZJxfY0uhYQ=; b=Nh9rWgxW8RsUDBLY/maB7XWaiRye14md8HFNcXV/s5AWueOvLGyMkhxBxIfWL2ckfe 0yMG9FJ/c/5ZDbTx1JAcTC3KdNbAJeZ5xP5SzHcJEmQu6hW4tXKEV6CQ80ZC6WrLATy1 mcV/dZbY8teweRXZPIGHNWYDXjgY8Js8/OaIW2HTsAUn/Mp/pPpXKghFDzGg8Vk5LkFB V48PF1clL5b0e66U57C1lOAYezah8mIv/4GCJCruKkFnBf1K44tBAzL/tuVEtMh+Kz73 Hj0aX47ZkBV2u/sgXsF+AECf0ZWnaCMrYwNxK/9CXsFo9F2iMETawh8K7S/8q+rLSFIQ 9P2A== X-Gm-Message-State: AOAM530MQgwfAc1iQQeYTpacI8hOGc1Vq9bp10YnpN/6o8S6PDeg2osc iAdGpWQBN6cs1L+RqvKGVV7TONn5xOCX0Xc8rsxDM4G8El9v X-Google-Smtp-Source: ABdhPJzIsgdiwElT0nZcwjdSSUK7orxipUME4z4qUz1YAzvQj8yY2z8kXyRF+7YmOSO9l1A0KS/2JVcd7AwNMEDomew6PQ3soPZ7 MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1908:: with SMTP id w8mr6245044ilu.229.1611115165061; Tue, 19 Jan 2021 19:59:25 -0800 (PST) Date: Tue, 19 Jan 2021 19:59:25 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000001b164705b94cfb58@google.com> Subject: WARNING: suspicious RCU usage in inode_security 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: 82821be8 Merge tag 'arm64-fixes' of git://git.kernel.org/p.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14a3da20d00000 kernel config: https://syzkaller.appspot.com/x/.config?x=70f222f8a2ffcbde dashboard link: https://syzkaller.appspot.com/bug?extid=37978b81dea56c7a4249 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+37978b81dea56c7a4249@syzkaller.appspotmail.com ============================= WARNING: suspicious RCU usage 5.11.0-rc3-syzkaller #0 Not tainted ----------------------------- kernel/sched/core.c:7867 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 1 lock held by kworker/u17:3/10446: #0: ffff888014f94c00 (&sig->cred_guard_mutex){+.+.}-{3:3}, at: prepare_bprm_creds fs/exec.c:1462 [inline] #0: ffff888014f94c00 (&sig->cred_guard_mutex){+.+.}-{3:3}, at: bprm_execve+0xb2/0x19a0 fs/exec.c:1794 stack backtrace: CPU: 1 PID: 10446 Comm: kworker/u17:3 Not tainted 5.11.0-rc3-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:79 [inline] dump_stack+0x107/0x163 lib/dump_stack.c:120 ___might_sleep+0x229/0x2c0 kernel/sched/core.c:7867 __inode_security_revalidate security/selinux/hooks.c:259 [inline] inode_security+0x5d/0x130 security/selinux/hooks.c:296 selinux_file_permission+0x140/0x520 security/selinux/hooks.c:3549 security_file_permission+0x56/0x560 security/security.c:1448 rw_verify_area+0x115/0x350 fs/read_write.c:400 kernel_read+0x2a/0x70 fs/read_write.c:469 prepare_binprm fs/exec.c:1646 [inline] search_binary_handler fs/exec.c:1700 [inline] exec_binprm fs/exec.c:1757 [inline] bprm_execve fs/exec.c:1826 [inline] bprm_execve+0x740/0x19a0 fs/exec.c:1788 kernel_execve+0x370/0x460 fs/exec.c:1969 call_usermodehelper_exec_async+0x2de/0x580 kernel/umh.c:110 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296 --- 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.