=============================== [ INFO: suspicious RCU usage. ] 4.9.202+ #0 Not tainted ------------------------------- include/linux/radix-tree.h:199 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 0 2 locks held by syz-executor.0/32508: #0: (&sb->s_type->i_mutex_key#10){+.+.+.}, at: [<00000000a620ae99>] inode_lock include/linux/fs.h:771 [inline] #0: (&sb->s_type->i_mutex_key#10){+.+.+.}, at: [<00000000a620ae99>] shmem_add_seals+0x166/0x1020 mm/shmem.c:2610 #1: (&(&mapping->tree_lock)->rlock){..-...}, at: [<00000000aa71ee3a>] spin_lock_irq include/linux/spinlock.h:332 [inline] #1: (&(&mapping->tree_lock)->rlock){..-...}, at: [<00000000aa71ee3a>] shmem_tag_pins mm/shmem.c:2465 [inline] #1: (&(&mapping->tree_lock)->rlock){..-...}, at: [<00000000aa71ee3a>] shmem_wait_for_pins mm/shmem.c:2506 [inline] #1: (&(&mapping->tree_lock)->rlock){..-...}, at: [<00000000aa71ee3a>] shmem_add_seals+0x342/0x1020 mm/shmem.c:2622 stack backtrace: CPU: 1 PID: 32508 Comm: syz-executor.0 Not tainted 4.9.202+ #0 ffff8801ad2afca0 ffffffff81b55d2b ffff8801ace96908 0000000000000000 0000000000000002 00000000000000c7 ffff8801a0ae97c0 ffff8801ad2afcd0 ffffffff81406867 ffffea00065970c0 dffffc0000000000 ffff8801ad2afd78 Call Trace: [<0000000045174315>] __dump_stack lib/dump_stack.c:15 [inline] [<0000000045174315>] dump_stack+0xcb/0x130 lib/dump_stack.c:56 [<000000001cf87c9b>] lockdep_rcu_suspicious.cold+0x10a/0x149 kernel/locking/lockdep.c:4458 [<000000001d6a6c2e>] radix_tree_deref_slot include/linux/radix-tree.h:199 [inline] [<000000001d6a6c2e>] shmem_tag_pins mm/shmem.c:2467 [inline] [<000000001d6a6c2e>] shmem_wait_for_pins mm/shmem.c:2506 [inline] [<000000001d6a6c2e>] shmem_add_seals+0xa44/0x1020 mm/shmem.c:2622 [<000000000c7b3b33>] shmem_fcntl+0xf7/0x130 mm/shmem.c:2657 [<000000000f3f3e97>] do_fcntl fs/fcntl.c:340 [inline] [<000000000f3f3e97>] SYSC_fcntl fs/fcntl.c:376 [inline] [<000000000f3f3e97>] SyS_fcntl+0x1d5/0xb50 fs/fcntl.c:361 [<00000000f961736b>] do_syscall_64+0x1ad/0x5c0 arch/x86/entry/common.c:288 [<0000000066f8f918>] entry_SYSCALL_64_after_swapgs+0x5d/0xdb F2FS-fs (loop3): Magic Mismatch, valid(0xf2f52010) - read(0x0) F2FS-fs (loop3): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop3): Invalid segment/section count (14, 0 x 1) F2FS-fs (loop3): Can't find valid F2FS filesystem in 2th superblock F2FS-fs (loop3): Magic Mismatch, valid(0xf2f52010) - read(0x0) F2FS-fs (loop3): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop3): Invalid segment/section count (14, 0 x 1) F2FS-fs (loop3): Can't find valid F2FS filesystem in 2th superblock EXT4-fs (sda1): Test dummy encryption mount option ignored EXT4-fs (sda1): re-mounted. Opts: test_dummy_encryption, netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. IPv6: NLM_F_CREATE should be specified when creating new route IPv6: RTM_NEWROUTE with no NLM_F_CREATE or NLM_F_REPLACE IPv6: NLM_F_CREATE should be set when creating new route IPv6: NLM_F_CREATE should be set when creating new route IPv6: RTM_NEWROUTE with no NLM_F_CREATE or NLM_F_REPLACE IPv6: NLM_F_CREATE should be set when creating new route IPv6: RTM_NEWROUTE with no NLM_F_CREATE or NLM_F_REPLACE IPv6: RTM_NEWROUTE with no NLM_F_CREATE or NLM_F_REPLACE IPv6: RTM_NEWROUTE with no NLM_F_CREATE or NLM_F_REPLACE EXT4-fs (loop5): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock EXT4-fs (loop5): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock EXT4-fs (loop5): ext4_check_descriptors: Inode table for group 0 overlaps superblock EXT4-fs (loop5): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop4): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock EXT4-fs (loop4): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock EXT4-fs (loop4): ext4_check_descriptors: Inode table for group 0 overlaps superblock EXT4-fs error (device loop4): ext4_iget:4556: inode #2: comm syz-executor.4: root inode unallocated EXT4-fs (loop4): get root inode failed EXT4-fs (loop4): mount failed EXT4-fs (loop4): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock EXT4-fs (loop4): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock EXT4-fs (loop4): ext4_check_descriptors: Inode table for group 0 overlaps superblock EXT4-fs error (device loop4): ext4_iget:4556: inode #2: comm syz-executor.4: root inode unallocated EXT4-fs (loop4): get root inode failed EXT4-fs (loop4): mount failed EXT4-fs (loop4): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock EXT4-fs (loop4): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock EXT4-fs (loop4): ext4_check_descriptors: Inode table for group 0 overlaps superblock EXT4-fs error (device loop4): ext4_iget:4556: inode #2: comm syz-executor.4: root inode unallocated EXT4-fs (loop4): get root inode failed EXT4-fs (loop4): mount failed blk_update_request: I/O error, dev loop4, sector 0 F2FS-fs (loop4): Unable to read 1th superblock F2FS-fs (loop4): Magic Mismatch, valid(0xf2f52010) - read(0x0) F2FS-fs (loop4): Can't find valid F2FS filesystem in 2th superblock blk_update_request: I/O error, dev loop4, sector 0 F2FS-fs (loop4): Unable to read 1th superblock blk_update_request: I/O error, dev loop4, sector 8 F2FS-fs (loop4): Unable to read 2th superblock blk_update_request: I/O error, dev loop4, sector 0 F2FS-fs (loop4): Unable to read 1th superblock blk_update_request: I/O error, dev loop4, sector 8 F2FS-fs (loop4): Unable to read 2th superblock