Hello,
syzbot found the following issue on:
HEAD commit: 8020ae3c051d Linux 5.15.103
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=13f30ffcc80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=d4215fb4040f8f8d
dashboard link:
https://syzkaller.appspot.com/bug?extid=3750793de72b871c45e4
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/857e17de0f0a/disk-8020ae3c.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/9efc49fcd441/vmlinux-8020ae3c.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/f14c38b6bfa7/bzImage-8020ae3c.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+375079...@syzkaller.appspotmail.com
======================================================
WARNING: possible circular locking dependency detected
5.15.103-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.0/14599 is trying to acquire lock:
ffff8880247bc460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
but task is already holding lock:
ffff888068d17080 (&iint->mutex){+.+.}-{3:3}, at: process_measurement+0x733/0x1d60 security/integrity/ima/ima_main.c:260
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&iint->mutex){+.+.}-{3:3}:
lock_acquire+0x1ff/0x570 kernel/locking/lockdep.c:5622
__mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
process_measurement+0x733/0x1d60 security/integrity/ima/ima_main.c:260
ima_file_check+0xf3/0x180 security/integrity/ima/ima_main.c:519
do_open fs/namei.c:3540 [inline]
path_openat+0x2745/0x2f20 fs/namei.c:3672
do_filp_open+0x21c/0x460 fs/namei.c:3699
do_sys_openat2+0x13b/0x500 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1238
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
-> #0 (sb_writers#5){.+.+}-{0:0}:
check_prev_add kernel/locking/lockdep.c:3053 [inline]
check_prevs_add kernel/locking/lockdep.c:3172 [inline]
validate_chain+0x1646/0x58b0 kernel/locking/lockdep.c:3787
__lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
lock_acquire+0x1ff/0x570 kernel/locking/lockdep.c:5622
percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
__sb_start_write include/linux/fs.h:1742 [inline]
sb_start_write+0x4f/0x1c0 include/linux/fs.h:1812
mnt_want_write+0x3b/0x80 fs/namespace.c:377
ovl_maybe_copy_up+0x111/0x180 fs/overlayfs/copy_up.c:1074
ovl_open+0xa4/0x200 fs/overlayfs/file.c:150
do_dentry_open+0x807/0xfb0 fs/open.c:826
vfs_open fs/open.c:956 [inline]
dentry_open+0xc6/0x120 fs/open.c:972
ima_calc_file_hash+0x15f/0x1c00 security/integrity/ima/ima_crypto.c:558
ima_collect_measurement+0x293/0x530 security/integrity/ima/ima_api.c:254
process_measurement+0x1038/0x1d60 security/integrity/ima/ima_main.c:337
ima_file_check+0xf3/0x180 security/integrity/ima/ima_main.c:519
do_open fs/namei.c:3540 [inline]
path_openat+0x2745/0x2f20 fs/namei.c:3672
do_filp_open+0x21c/0x460 fs/namei.c:3699
do_sys_openat2+0x13b/0x500 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1238
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&iint->mutex);
lock(sb_writers#5);
lock(&iint->mutex);
lock(sb_writers#5);
*** DEADLOCK ***
1 lock held by syz-executor.0/14599:
#0: ffff888068d17080 (&iint->mutex){+.+.}-{3:3}, at: process_measurement+0x733/0x1d60 security/integrity/ima/ima_main.c:260
stack backtrace:
CPU: 1 PID: 14599 Comm: syz-executor.0 Not tainted 5.15.103-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
check_noncircular+0x2f8/0x3b0 kernel/locking/lockdep.c:2133
check_prev_add kernel/locking/lockdep.c:3053 [inline]
check_prevs_add kernel/locking/lockdep.c:3172 [inline]
validate_chain+0x1646/0x58b0 kernel/locking/lockdep.c:3787
__lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
lock_acquire+0x1ff/0x570 kernel/locking/lockdep.c:5622
percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
__sb_start_write include/linux/fs.h:1742 [inline]
sb_start_write+0x4f/0x1c0 include/linux/fs.h:1812
mnt_want_write+0x3b/0x80 fs/namespace.c:377
ovl_maybe_copy_up+0x111/0x180 fs/overlayfs/copy_up.c:1074
ovl_open+0xa4/0x200 fs/overlayfs/file.c:150
do_dentry_open+0x807/0xfb0 fs/open.c:826
vfs_open fs/open.c:956 [inline]
dentry_open+0xc6/0x120 fs/open.c:972
ima_calc_file_hash+0x15f/0x1c00 security/integrity/ima/ima_crypto.c:558
ima_collect_measurement+0x293/0x530 security/integrity/ima/ima_api.c:254
process_measurement+0x1038/0x1d60 security/integrity/ima/ima_main.c:337
ima_file_check+0xf3/0x180 security/integrity/ima/ima_main.c:519
do_open fs/namei.c:3540 [inline]
path_openat+0x2745/0x2f20 fs/namei.c:3672
do_filp_open+0x21c/0x460 fs/namei.c:3699
do_sys_openat2+0x13b/0x500 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1238
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f0e220f60f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0e20668168 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f0e22215f80 RCX: 00007f0e220f60f9
RDX: 0000000000000003 RSI: 0000000020000340 RDI: 0000000000000004
RBP: 00007f0e22151b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd1230800f R14: 00007f0e20668300 R15: 0000000000022000
</TASK>
---
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
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.