linux-kernel - WARNING: suspicious RCU usage in inode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <0000000000001b164705b94cfb58@google.com>
Date:   Tue, 19 Jan 2021 19:59:25 -0800
From:   syzbot <syzbot+37978b81dea56c7a4249@...kaller.appspotmail.com>
To:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk
Subject: WARNING: suspicious RCU usage in inode_security

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@...kaller.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@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.