new mount options do not match the existing superblock, will be ignored ====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/19414 is trying to acquire lock: new mount options do not match the existing superblock, will be ignored 00000000792ee67f (&ovl_i_mutex_key[depth]){+.+.}, at: inode_lock include/linux/fs.h:748 [inline] 00000000792ee67f (&ovl_i_mutex_key[depth]){+.+.}, at: ovl_write_iter+0x148/0xb40 fs/overlayfs/file.c:270 but task is already holding lock: 000000008101c68d (&pipe->mutex/1){+.+.}, at: pipe_lock_nested fs/pipe.c:77 [inline] 000000008101c68d (&pipe->mutex/1){+.+.}, at: pipe_lock fs/pipe.c:85 [inline] 000000008101c68d (&pipe->mutex/1){+.+.}, at: pipe_wait+0x1bd/0x1e0 fs/pipe.c:133 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&pipe->mutex/1){+.+.}: pipe_lock_nested fs/pipe.c:77 [inline] pipe_lock+0x63/0x80 fs/pipe.c:85 iter_file_splice_write+0x183/0xbb0 fs/splice.c:700 do_splice_from fs/splice.c:852 [inline] do_splice fs/splice.c:1154 [inline] __do_sys_splice fs/splice.c:1428 [inline] __se_sys_splice+0xfe7/0x16d0 fs/splice.c:1408 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #2 (sb_writers#3){.+.+}: sb_start_write include/linux/fs.h:1579 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:360 ovl_rename+0x22b/0x1a50 fs/overlayfs/dir.c:1084 vfs_rename+0x67e/0x1bc0 fs/namei.c:4479 do_renameat2+0xb59/0xc70 fs/namei.c:4629 __do_sys_renameat2 fs/namei.c:4664 [inline] __se_sys_renameat2 fs/namei.c:4661 [inline] __x64_sys_renameat2+0xba/0x150 fs/namei.c:4661 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #1 (&ovl_i_mutex_key[depth]/4){+.+.}: inode_lock_nested include/linux/fs.h:783 [inline] lock_two_nondirectories+0xd1/0x110 fs/inode.c:1017 vfs_rename+0x3cb/0x1bc0 fs/namei.c:4453 do_renameat2+0xb59/0xc70 fs/namei.c:4629 __do_sys_renameat2 fs/namei.c:4664 [inline] __se_sys_renameat2 fs/namei.c:4661 [inline] __x64_sys_renameat2+0xba/0x150 fs/namei.c:4661 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&ovl_i_mutex_key[depth]){+.+.}: down_write+0x34/0x90 kernel/locking/rwsem.c:70 inode_lock include/linux/fs.h:748 [inline] ovl_write_iter+0x148/0xb40 fs/overlayfs/file.c:270 call_write_iter include/linux/fs.h:1821 [inline] new_sync_write fs/read_write.c:474 [inline] __vfs_write+0x51b/0x770 fs/read_write.c:487 __kernel_write+0x109/0x370 fs/read_write.c:506 write_pipe_buf+0x153/0x1f0 fs/splice.c:798 splice_from_pipe_feed fs/splice.c:503 [inline] __splice_from_pipe+0x389/0x800 fs/splice.c:627 splice_from_pipe fs/splice.c:662 [inline] default_file_splice_write+0xd8/0x180 fs/splice.c:810 do_splice_from fs/splice.c:852 [inline] do_splice fs/splice.c:1154 [inline] __do_sys_splice fs/splice.c:1428 [inline] __se_sys_splice+0xfe7/0x16d0 fs/splice.c:1408 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Chain exists of: &ovl_i_mutex_key[depth] --> sb_writers#3 --> &pipe->mutex/1 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&pipe->mutex/1); lock(sb_writers#3); lock(&pipe->mutex/1); lock(&ovl_i_mutex_key[depth]); *** DEADLOCK *** 2 locks held by syz-executor.0/19414: #0: 000000002fdea471 (sb_writers#16){.+.+}, at: file_start_write include/linux/fs.h:2779 [inline] #0: 000000002fdea471 (sb_writers#16){.+.+}, at: do_splice fs/splice.c:1153 [inline] #0: 000000002fdea471 (sb_writers#16){.+.+}, at: __do_sys_splice fs/splice.c:1428 [inline] #0: 000000002fdea471 (sb_writers#16){.+.+}, at: __se_sys_splice+0x11de/0x16d0 fs/splice.c:1408 #1: 000000008101c68d (&pipe->mutex/1){+.+.}, at: pipe_lock_nested fs/pipe.c:77 [inline] #1: 000000008101c68d (&pipe->mutex/1){+.+.}, at: pipe_lock fs/pipe.c:85 [inline] #1: 000000008101c68d (&pipe->mutex/1){+.+.}, at: pipe_wait+0x1bd/0x1e0 fs/pipe.c:133 stack backtrace: CPU: 1 PID: 19414 Comm: syz-executor.0 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1222 check_prev_add kernel/locking/lockdep.c:1866 [inline] check_prevs_add kernel/locking/lockdep.c:1979 [inline] validate_chain kernel/locking/lockdep.c:2420 [inline] __lock_acquire+0x30c9/0x3ff0 kernel/locking/lockdep.c:3416 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908 down_write+0x34/0x90 kernel/locking/rwsem.c:70 inode_lock include/linux/fs.h:748 [inline] ovl_write_iter+0x148/0xb40 fs/overlayfs/file.c:270 call_write_iter include/linux/fs.h:1821 [inline] new_sync_write fs/read_write.c:474 [inline] __vfs_write+0x51b/0x770 fs/read_write.c:487 __kernel_write+0x109/0x370 fs/read_write.c:506 write_pipe_buf+0x153/0x1f0 fs/splice.c:798 splice_from_pipe_feed fs/splice.c:503 [inline] __splice_from_pipe+0x389/0x800 fs/splice.c:627 splice_from_pipe fs/splice.c:662 [inline] default_file_splice_write+0xd8/0x180 fs/splice.c:810 do_splice_from fs/splice.c:852 [inline] do_splice fs/splice.c:1154 [inline] __do_sys_splice fs/splice.c:1428 [inline] __se_sys_splice+0xfe7/0x16d0 fs/splice.c:1408 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7f05c5d3e0d9 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:00007f05c42b0168 EFLAGS: 00000246 ORIG_RAX: 0000000000000113 RAX: ffffffffffffffda RBX: 00007f05c5e5df80 RCX: 00007f05c5d3e0d9 RDX: 0000000000000005 RSI: 0000000000000000 RDI: 0000000000000004 RBP: 00007f05c5d99ae9 R08: 000000000000fdef R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffdce7b711f R14: 00007f05c42b0300 R15: 0000000000022000 EXT4-fs (loop5): feature flags set on rev 0 fs, running e2fsck is recommended can: request_module (can-proto-6) failed. nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. EXT4-fs (loop5): orphan cleanup on readonly fs Quota error (device loop5): v2_read_file_info: Block with free entry too big (517 >= 6). EXT4-fs warning (device loop5): ext4_enable_quotas:5883: Failed to enable quota tracking (type=0, err=-117). Please run e2fsck to fix. EXT4-fs (loop5): Cannot turn on quotas: error -117 EXT4-fs warning (device loop5): ext4_update_dynamic_rev:860: updating to rev 1 because of new feature flag, running e2fsck is recommended can: request_module (can-proto-6) failed. EXT4-fs error (device loop5): ext4_mb_generate_buddy:744: group 0, block bitmap and bg descriptor inconsistent: 100 vs 41 free clusters EXT4-fs (loop5): 1 truncate cleaned up EXT4-fs (loop5): mounted filesystem without journal. Opts: bsdgroups,,errors=continue EXT4-fs (loop5): feature flags set on rev 0 fs, running e2fsck is recommended EXT4-fs (loop5): orphan cleanup on readonly fs Quota error (device loop5): v2_read_file_info: Block with free entry too big (517 >= 6). EXT4-fs warning (device loop5): ext4_enable_quotas:5883: Failed to enable quota tracking (type=0, err=-117). Please run e2fsck to fix. can: request_module (can-proto-6) failed. EXT4-fs (loop5): Cannot turn on quotas: error -117 EXT4-fs warning (device loop5): ext4_update_dynamic_rev:860: updating to rev 1 because of new feature flag, running e2fsck is recommended EXT4-fs error (device loop5): ext4_mb_generate_buddy:744: group 0, block bitmap and bg descriptor inconsistent: 100 vs 41 free clusters EXT4-fs (loop5): 1 truncate cleaned up EXT4-fs (loop5): mounted filesystem without journal. Opts: bsdgroups,,errors=continue can: request_module (can-proto-6) failed. f2fs_msg: 5 callbacks suppressed F2FS-fs (loop1): Mismatch start address, segment0(512) cp_blkaddr(605) F2FS-fs (loop1): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop1): Failed to initialize F2FS segment manager F2FS-fs (loop1): Mismatch start address, segment0(512) cp_blkaddr(605) F2FS-fs (loop1): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop1): Failed to initialize F2FS segment manager can: request_module (can-proto-6) failed. can: request_module (can-proto-6) failed. nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. EXT4-fs (loop5): feature flags set on rev 0 fs, running e2fsck is recommended can: request_module (can-proto-6) failed. nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. EXT4-fs (loop5): orphan cleanup on readonly fs Quota error (device loop5): v2_read_file_info: Block with free entry too big (517 >= 6). EXT4-fs warning (device loop5): ext4_enable_quotas:5883: Failed to enable quota tracking (type=0, err=-117). Please run e2fsck to fix. EXT4-fs (loop5): Cannot turn on quotas: error -117 EXT4-fs warning (device loop5): ext4_update_dynamic_rev:860: updating to rev 1 because of new feature flag, running e2fsck is recommended EXT4-fs error (device loop5): ext4_mb_generate_buddy:744: group 0, block bitmap and bg descriptor inconsistent: 100 vs 41 free clusters EXT4-fs (loop5): 1 truncate cleaned up EXT4-fs (loop5): mounted filesystem without journal. Opts: bsdgroups,,errors=continue EXT4-fs (loop5): feature flags set on rev 0 fs, running e2fsck is recommended EXT4-fs (loop5): orphan cleanup on readonly fs Quota error (device loop5): v2_read_file_info: Block with free entry too big (517 >= 6). can: request_module (can-proto-6) failed. EXT4-fs warning (device loop5): ext4_enable_quotas:5883: Failed to enable quota tracking (type=0, err=-117). Please run e2fsck to fix. EXT4-fs (loop5): Cannot turn on quotas: error -117 EXT4-fs warning (device loop5): ext4_update_dynamic_rev:860: updating to rev 1 because of new feature flag, running e2fsck is recommended EXT4-fs error (device loop5): ext4_mb_generate_buddy:744: group 0, block bitmap and bg descriptor inconsistent: 100 vs 41 free clusters nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. EXT4-fs (loop5): 1 truncate cleaned up EXT4-fs (loop5): mounted filesystem without journal. Opts: bsdgroups,,errors=continue can: request_module (can-proto-6) failed. can: request_module (can-proto-6) failed. nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. can_create: 5 callbacks suppressed can: request_module (can-proto-6) failed. can: request_module (can-proto-6) failed. REISERFS (device loop2): found reiserfs format "3.6" with non-standard journal can: request_module (can-proto-6) failed. REISERFS (device loop2): using ordered data mode reiserfs: using flush barriers REISERFS (device loop2): journal params: device loop2, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop2): checking transaction log (loop2) REISERFS (device loop2): Using r5 hash to sort names REISERFS (device loop2): Created .reiserfs_priv - reserved for xattr storage. can: request_module (can-proto-6) failed. IPVS: ftp: loaded support on port[0] = 21 REISERFS (device loop2): found reiserfs format "3.6" with non-standard journal REISERFS (device loop2): using ordered data mode reiserfs: using flush barriers REISERFS (device loop2): journal params: device loop2, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop2): checking transaction log (loop2) EXT4-fs warning (device sda1): ext4_resize_begin:72: There are errors in the filesystem, so online resizing is not allowed REISERFS (device loop2): Using r5 hash to sort names REISERFS (device loop2): Created .reiserfs_priv - reserved for xattr storage. IPVS: ftp: loaded support on port[0] = 21 EXT4-fs warning (device sda1): ext4_resize_begin:72: There are errors in the filesystem, so online resizing is not allowed BTRFS: device fsid a6a605fc-d5f1-4e66-8595-3726e2b761d6 devid 1 transid 8 /dev/loop1 BTRFS error (device loop1): unsupported checksum algorithm 3 BTRFS error (device loop1): superblock checksum mismatch BTRFS error (device loop1): open_ctree failed REISERFS (device loop2): found reiserfs format "3.6" with non-standard journal REISERFS (device loop2): using ordered data mode reiserfs: using flush barriers REISERFS (device loop2): journal params: device loop2, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop2): checking transaction log (loop2) REISERFS (device loop2): Using r5 hash to sort names REISERFS (device loop2): Created .reiserfs_priv - reserved for xattr storage. IPVS: ftp: loaded support on port[0] = 21 syz-executor.1 (19716): drop_caches: 2 syz-executor.1 (19716): drop_caches: 2