netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ kworker/u4:0/13147 is trying to acquire lock: 00000000354c7524 (&rl->lock){++++}, at: ntfs_read_block fs/ntfs/aops.c:265 [inline] 00000000354c7524 (&rl->lock){++++}, at: ntfs_readpage+0x1909/0x21b0 fs/ntfs/aops.c:452 but task is already holding lock: 000000007608226f (&ni->mrec_lock){+.+.}, at: map_mft_record+0x3c/0xc70 fs/ntfs/mft.c:168 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ni->mrec_lock){+.+.}: map_mft_record+0x3c/0xc70 fs/ntfs/mft.c:168 ntfs_truncate+0x202/0x2820 fs/ntfs/inode.c:2395 ntfs_truncate_vfs fs/ntfs/inode.c:2875 [inline] ntfs_setattr+0x1b6/0x620 fs/ntfs/inode.c:2925 notify_change+0x70b/0xfc0 fs/attr.c:334 do_truncate+0x134/0x1f0 fs/open.c:63 vfs_truncate+0x54b/0x6d0 fs/open.c:109 do_sys_truncate fs/open.c:132 [inline] do_sys_truncate+0x145/0x170 fs/open.c:120 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&rl->lock){++++}: down_read+0x36/0x80 kernel/locking/rwsem.c:24 ntfs_read_block fs/ntfs/aops.c:265 [inline] ntfs_readpage+0x1909/0x21b0 fs/ntfs/aops.c:452 do_read_cache_page+0x533/0x1170 mm/filemap.c:2828 read_mapping_page include/linux/pagemap.h:402 [inline] ntfs_map_page fs/ntfs/aops.h:89 [inline] ntfs_sync_mft_mirror+0x24f/0x1d00 fs/ntfs/mft.c:494 write_mft_record_nolock+0x13d2/0x16c0 fs/ntfs/mft.c:801 write_mft_record fs/ntfs/mft.h:109 [inline] __ntfs_write_inode+0x609/0xe10 fs/ntfs/inode.c:3064 write_inode fs/fs-writeback.c:1244 [inline] __writeback_single_inode+0x733/0x11d0 fs/fs-writeback.c:1442 writeback_sb_inodes+0x537/0xef0 fs/fs-writeback.c:1647 wb_writeback+0x28d/0xcc0 fs/fs-writeback.c:1820 wb_do_writeback fs/fs-writeback.c:1965 [inline] wb_workfn+0x29b/0x1250 fs/fs-writeback.c:2006 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->mrec_lock); lock(&rl->lock); lock(&ni->mrec_lock); lock(&rl->lock); *** DEADLOCK *** 3 locks held by kworker/u4:0/13147: #0: 000000005b41a4cd ((wq_completion)"writeback"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124 #1: 000000003f1d5bdd ((work_completion)(&(&wb->dwork)->work)){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128 #2: 000000007608226f (&ni->mrec_lock){+.+.}, at: map_mft_record+0x3c/0xc70 fs/ntfs/mft.c:168 stack backtrace: CPU: 1 PID: 13147 Comm: kworker/u4:0 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Workqueue: writeback wb_workfn (flush-7:5) 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_read+0x36/0x80 kernel/locking/rwsem.c:24 ntfs_read_block fs/ntfs/aops.c:265 [inline] ntfs_readpage+0x1909/0x21b0 fs/ntfs/aops.c:452 do_read_cache_page+0x533/0x1170 mm/filemap.c:2828 read_mapping_page include/linux/pagemap.h:402 [inline] ntfs_map_page fs/ntfs/aops.h:89 [inline] ntfs_sync_mft_mirror+0x24f/0x1d00 fs/ntfs/mft.c:494 write_mft_record_nolock+0x13d2/0x16c0 fs/ntfs/mft.c:801 write_mft_record fs/ntfs/mft.h:109 [inline] __ntfs_write_inode+0x609/0xe10 fs/ntfs/inode.c:3064 write_inode fs/fs-writeback.c:1244 [inline] __writeback_single_inode+0x733/0x11d0 fs/fs-writeback.c:1442 writeback_sb_inodes+0x537/0xef0 fs/fs-writeback.c:1647 wb_writeback+0x28d/0xcc0 fs/fs-writeback.c:1820 wb_do_writeback fs/fs-writeback.c:1965 [inline] wb_workfn+0x29b/0x1250 fs/fs-writeback.c:2006 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 ntfs: volume version 3.1. netlink: 'syz-executor.2': attribute type 1 has an invalid length. IPv6: ADDRCONF(NETDEV_UP): bond2661: link is not ready 8021q: adding VLAN 0 to HW filter on device bond2661 ntfs: volume version 3.1. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ntfs: volume version 3.1. ntfs: volume version 3.1. netlink: 'syz-executor.2': attribute type 1 has an invalid length. ntfs: volume version 3.1. ntfs: volume version 3.1. IPv6: ADDRCONF(NETDEV_UP): bond2662: link is not ready 8021q: adding VLAN 0 to HW filter on device bond2662 netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ntfs: volume version 3.1. ntfs: volume version 3.1. netlink: 'syz-executor.2': attribute type 1 has an invalid length. IPv6: ADDRCONF(NETDEV_UP): bond2663: link is not ready ntfs: volume version 3.1. 8021q: adding VLAN 0 to HW filter on device bond2663 bond2663: making interface bridge1987 the new active one bond2663: Enslaving bridge1987 as an active interface with an up link IPv6: ADDRCONF(NETDEV_CHANGE): bond2663: link becomes ready ntfs: volume version 3.1. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 'syz-executor.2': attribute type 1 has an invalid length. ntfs: volume version 3.1. ntfs: volume version 3.1. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 'syz-executor.2': attribute type 1 has an invalid length. IPv6: ADDRCONF(NETDEV_UP): bond2664: link is not ready 8021q: adding VLAN 0 to HW filter on device bond2664 ntfs: volume version 3.1. bond2664: making interface bridge1988 the new active one bond2664: Enslaving bridge1988 as an active interface with an up link IPv6: ADDRCONF(NETDEV_CHANGE): bond2664: link becomes ready netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ntfs: volume version 3.1. netlink: 'syz-executor.2': attribute type 1 has an invalid length. ntfs: volume version 3.1. IPv6: ADDRCONF(NETDEV_UP): bond2665: link is not ready 8021q: adding VLAN 0 to HW filter on device bond2665 bond2665: making interface bridge1989 the new active one bond2665: Enslaving bridge1989 as an active interface with an up link IPv6: ADDRCONF(NETDEV_CHANGE): bond2665: link becomes ready netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ntfs: volume version 3.1. ntfs: volume version 3.1. netlink: 'syz-executor.2': attribute type 1 has an invalid length. bond2666 (uninitialized): Released all slaves netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ntfs: volume version 3.1. ntfs: volume version 3.1. netlink: 'syz-executor.2': attribute type 1 has an invalid length. IPv6: ADDRCONF(NETDEV_UP): bond2666: link is not ready 8021q: adding VLAN 0 to HW filter on device bond2666 netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ntfs: volume version 3.1. netlink: 'syz-executor.2': attribute type 1 has an invalid length. ntfs: volume version 3.1. IPv6: ADDRCONF(NETDEV_UP): bond2667: link is not ready 8021q: adding VLAN 0 to HW filter on device bond2667 ntfs: volume version 3.1. bond2667: making interface bridge1992 the new active one bond2667: Enslaving bridge1992 as an active interface with an up link IPv6: ADDRCONF(NETDEV_CHANGE): bond2667: link becomes ready netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ntfs: volume version 3.1. netlink: 'syz-executor.2': attribute type 1 has an invalid length. ntfs: volume version 3.1. IPv6: ADDRCONF(NETDEV_UP): bond2668: link is not ready 8021q: adding VLAN 0 to HW filter on device bond2668 bond2668: making interface bridge1993 the new active one bond2668: Enslaving bridge1993 as an active interface with an up link netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ntfs: volume version 3.1. IPv6: ADDRCONF(NETDEV_CHANGE): bond2668: link becomes ready netlink: 'syz-executor.2': attribute type 1 has an invalid length. IPv6: ADDRCONF(NETDEV_UP): bond2669: link is not ready ntfs: volume version 3.1. 8021q: adding VLAN 0 to HW filter on device bond2669 ntfs: volume version 3.1. bond2669: making interface bridge1994 the new active one bond2669: Enslaving bridge1994 as an active interface with an up link IPv6: ADDRCONF(NETDEV_CHANGE): bond2669: link becomes ready ntfs: volume version 3.1. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 'syz-executor.2': attribute type 1 has an invalid length. ntfs: volume version 3.1. IPv6: ADDRCONF(NETDEV_UP): bond2670: link is not ready 8021q: adding VLAN 0 to HW filter on device bond2670 ntfs: volume version 3.1. bond2670: making interface bridge1995 the new active one bond2670: Enslaving bridge1995 as an active interface with an up link ntfs: volume version 3.1. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ntfs: volume version 3.1. IPv6: ADDRCONF(NETDEV_CHANGE): bond2670: link becomes ready netlink: 'syz-executor.2': attribute type 1 has an invalid length.