======================================================
WARNING: possible circular locking dependency detected
6.12.0-rc4-syzkaller #0 Not tainted
------------------------------------------------------
syz.2.15/3374 is trying to acquire lock:
ffff888111f3cb98 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0x92/0x100 mm/memory.c:6705

but task is already holding lock:
ffff8881033de9e0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xe3/0x8a0 kernel/trace/blktrace.c:735

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (&q->debugfs_mutex){+.+.}-{3:3}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
       __mutex_lock_common kernel/locking/mutex.c:608 [inline]
       __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752
       blk_mq_init_sched+0x39f/0x730 block/blk-mq-sched.c:473
       elevator_init_mq+0x15f/0x240 block/elevator.c:605
       add_disk_fwnode+0xfe/0xd20 block/genhd.c:413
       sd_probe+0xa26/0x1060 drivers/scsi/sd.c:4024
       really_probe+0x258/0x8d0 drivers/base/dd.c:658
       __driver_probe_device+0x138/0x310 drivers/base/dd.c:800
       driver_probe_device+0x4b/0x3a0 drivers/base/dd.c:830
       __driver_attach_async_helper+0x133/0x250 drivers/base/dd.c:1148
       async_run_entry_fn+0x9e/0x3f0 kernel/async.c:129
       process_one_work kernel/workqueue.c:3229 [inline]
       process_scheduled_works+0x96c/0x1540 kernel/workqueue.c:3310
       worker_thread+0x727/0xb10 kernel/workqueue.c:3391
       kthread+0x2e0/0x380 kernel/kthread.c:389
       ret_from_fork+0x32/0x60 arch/x86/kernel/process.c:147
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

-> #3 (&q->q_usage_counter(io)#66){++++}-{0:0}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
       bio_queue_enter block/blk.h:75 [inline]
       blk_mq_submit_bio+0x7b5/0x1e10 block/blk-mq.c:3069
       __submit_bio+0x29b/0x510 block/blk-core.c:629
       __submit_bio_noacct_mq block/blk-core.c:710 [inline]
       submit_bio_noacct_nocheck+0x422/0xdf0 block/blk-core.c:739
       ext4_mpage_readpages+0x128e/0x13d0 fs/ext4/readpage.c:389
       read_pages+0x12e/0x650 mm/readahead.c:160
       page_cache_ra_unbounded+0x1ab/0x700 mm/readahead.c:290
       page_cache_sync_readahead include/linux/pagemap.h:1394 [inline]
       filemap_get_pages+0x53b/0x1ee0 mm/filemap.c:2547
       filemap_read+0x3ba/0xbd0 mm/filemap.c:2645
       __kernel_read+0x46d/0x850 fs/read_write.c:527
       prepare_binprm fs/exec.c:1687 [inline]
       search_binary_handler fs/exec.c:1736 [inline]
       exec_binprm fs/exec.c:1794 [inline]
       bprm_execve+0x8ca/0x1410 fs/exec.c:1845
       kernel_execve+0x741/0x830 fs/exec.c:2012
       try_to_run_init_process init/main.c:1397 [inline]
       kernel_init+0xdd/0x1b0 init/main.c:1525
       ret_from_fork+0x32/0x60 arch/x86/kernel/process.c:147
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

-> #2 (mapping.invalidate_lock){++++}-{3:3}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
       down_read+0xb1/0xa40 kernel/locking/rwsem.c:1524
       filemap_invalidate_lock_shared include/linux/fs.h:870 [inline]
       filemap_fault+0x682/0x1330 mm/filemap.c:3331
       __do_fault+0x10f/0x310 mm/memory.c:4871
       do_read_fault mm/memory.c:5286 [inline]
       do_fault mm/memory.c:5420 [inline]
       do_pte_missing mm/memory.c:3965 [inline]
       handle_pte_fault mm/memory.c:5755 [inline]
       __handle_mm_fault mm/memory.c:5898 [inline]
       handle_mm_fault+0x1890/0x4b40 mm/memory.c:6066
       do_user_addr_fault arch/x86/mm/fault.c:1338 [inline]
       handle_page_fault arch/x86/mm/fault.c:1481 [inline]
       exc_page_fault+0x409/0x830 arch/x86/mm/fault.c:1539
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623

-> #1 (&vma->vm_lock->lock){++++}-{3:3}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
       down_write+0x99/0x220 kernel/locking/rwsem.c:1577
       vma_start_write include/linux/mm.h:757 [inline]
       vma_link+0x22c/0x480 mm/vma.c:1596
       insert_vm_struct+0x299/0x370 mm/mmap.c:1946
       __bprm_mm_init fs/exec.c:289 [inline]
       bprm_mm_init fs/exec.c:393 [inline]
       alloc_bprm+0x6ea/0xb70 fs/exec.c:1548
       kernel_execve+0x79/0x830 fs/exec.c:1977
       try_to_run_init_process init/main.c:1397 [inline]
       kernel_init+0xdd/0x1b0 init/main.c:1525
       ret_from_fork+0x32/0x60 arch/x86/kernel/process.c:147
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

-> #0 (&mm->mmap_lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3161 [inline]
       check_prevs_add kernel/locking/lockdep.c:3280 [inline]
       validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904
       __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5202
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
       __might_fault+0xab/0x100 mm/memory.c:6705
       _inline_copy_from_user include/linux/uaccess.h:161 [inline]
       _copy_from_user+0x25/0xa0 lib/usercopy.c:18
       copy_from_user include/linux/uaccess.h:203 [inline]
       __blk_trace_setup kernel/trace/blktrace.c:626 [inline]
       blk_trace_ioctl+0x1b2/0x8a0 kernel/trace/blktrace.c:740
       blkdev_ioctl+0x3d8/0x5b0 block/ioctl.c:682
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:907 [inline]
       __se_sys_ioctl+0xa8/0xf0 fs/ioctl.c:893
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &mm->mmap_lock --> &q->q_usage_counter(io)#66 --> &q->debugfs_mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&q->debugfs_mutex);
                               lock(&q->q_usage_counter(io)#66);
                               lock(&q->debugfs_mutex);
  rlock(&mm->mmap_lock);

 *** DEADLOCK ***

1 lock held by syz.2.15/3374:
 #0: ffff8881033de9e0 (&q->debugfs_mutex){+.+.}-{3:3}, at: blk_trace_ioctl+0xe3/0x8a0 kernel/trace/blktrace.c:735

stack backtrace:
CPU: 0 UID: 0 PID: 3374 Comm: syz.2.15 Not tainted 6.12.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x198/0x250 lib/dump_stack.c:120
 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2074
 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2206
 check_prev_add kernel/locking/lockdep.c:3161 [inline]
 check_prevs_add kernel/locking/lockdep.c:3280 [inline]
 validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904
 __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5202
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
 __might_fault+0xab/0x100 mm/memory.c:6705
 _inline_copy_from_user include/linux/uaccess.h:161 [inline]
 _copy_from_user+0x25/0xa0 lib/usercopy.c:18
 copy_from_user include/linux/uaccess.h:203 [inline]
 __blk_trace_setup kernel/trace/blktrace.c:626 [inline]
 blk_trace_ioctl+0x1b2/0x8a0 kernel/trace/blktrace.c:740
 blkdev_ioctl+0x3d8/0x5b0 block/ioctl.c:682
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:907 [inline]
 __se_sys_ioctl+0xa8/0xf0 fs/ioctl.c:893
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f67bd37e719
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f67be21f038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f67bd535f80 RCX: 00007f67bd37e719
RDX: 0000000000000000 RSI: 00000000c0481273 RDI: 0000000000000003
RBP: 00007f67bd3f139e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f67bd535f80 R15: 00007ffe6b811588
 </TASK>