warning: checkpointing journal with EXT4_IOC_CHECKPOINT_FLAG_ZEROOUT can be slow
======================================================
WARNING: possible circular locking dependency detected
5.19.0-next-20220812 #1 Not tainted
------------------------------------------------------
syz-executor.0/11511 is trying to acquire lock:
ffff88800bdb0400 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: ext4_bmap+0x4e/0x470
but task is already holding lock:
ffff88800fe5e3f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc00
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #3 (&journal->j_checkpoint_mutex){+.+.}-{3:3}:
mutex_lock_io_nested+0x148/0x1310
jbd2_journal_flush+0x19a/0xc00
__ext4_ioctl+0x9e9/0x4090
__x64_sys_ioctl+0x19a/0x210
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #2 (&journal->j_barrier){+.+.}-{3:3}:
__mutex_lock+0x136/0x14d0
jbd2_journal_lock_updates+0x15e/0x310
ext4_change_inode_journal_flag+0x17f/0x530
ext4_fileattr_set+0x140d/0x18a0
vfs_fileattr_set+0x77c/0xb80
do_vfs_ioctl+0xfc2/0x1610
__x64_sys_ioctl+0x10c/0x210
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #1 (&sbi->s_writepages_rwsem){++++}-{0:0}:
percpu_down_write+0x4d/0x3d0
ext4_ind_migrate+0x237/0x830
ext4_fileattr_set+0x1434/0x18a0
vfs_fileattr_set+0x77c/0xb80
do_vfs_ioctl+0xfc2/0x1610
__x64_sys_ioctl+0x10c/0x210
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #0 (&sb->s_type->i_mutex_key#6){++++}-{3:3}:
__lock_acquire+0x2a02/0x5e70
lock_acquire+0x1a2/0x530
down_read+0x98/0x450
ext4_bmap+0x4e/0x470
bmap+0xac/0x120
jbd2_journal_bmap+0xa8/0x180
jbd2_journal_flush+0x853/0xc00
__ext4_ioctl+0x9e9/0x4090
__x64_sys_ioctl+0x19a/0x210
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
other info that might help us debug this:
Chain exists of:
&sb->s_type->i_mutex_key#6 --> &journal->j_barrier --> &journal->j_checkpoint_mutex
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&journal->j_checkpoint_mutex);
lock(&journal->j_barrier);
lock(&journal->j_checkpoint_mutex);
lock(&sb->s_type->i_mutex_key#6);
*** DEADLOCK ***
2 locks held by syz-executor.0/11511:
#0: ffff88800fe5e170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x15e/0x310
#1: ffff88800fe5e3f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc00
stack backtrace:
CPU: 1 PID: 11511 Comm: syz-executor.0 Not tainted 5.19.0-next-20220812 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Call Trace:
dump_stack_lvl+0x8b/0xb3
check_noncircular+0x263/0x2e0
__lock_acquire+0x2a02/0x5e70
lock_acquire+0x1a2/0x530
down_read+0x98/0x450
ext4_bmap+0x4e/0x470
bmap+0xac/0x120
jbd2_journal_bmap+0xa8/0x180
jbd2_journal_flush+0x853/0xc00
__ext4_ioctl+0x9e9/0x4090
__x64_sys_ioctl+0x19a/0x210
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f0e9ed60b19
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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0e9c2d6188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f0e9ee73f60 RCX: 00007f0e9ed60b19
RDX: 0000000020000340 RSI: 000000004004662b RDI: 0000000000000005
RBP: 00007f0e9edbaf6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe94eef92f R14: 00007f0e9c2d6300 R15: 0000000000022000
9pnet_fd: p9_fd_create_tcp (11474): problem connecting socket to 127.0.0.1
netlink: 12 bytes leftover after parsing attributes in process `syz-executor.2'.
ieee80211 phy34: Selected rate control algorithm 'minstrel_ht'
netlink: 200 bytes leftover after parsing attributes in process `syz-executor.2'.
systemd[1]: systemd-journald.service: Main process exited, code=killed, status=6/ABRT
systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
systemd[1]: systemd-journald.service: Consumed 37.370s CPU time.
systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
systemd[1]: Stopping Flush Journal to Persistent Storage...
systemd[1]: systemd-journal-flush.service: Succeeded.
systemd[1]: Stopped Flush Journal to Persistent Storage.
systemd[1]: Stopped Journal Service.
systemd[1]: systemd-journald.service: Consumed 37.370s CPU time.
systemd[1]: Starting Journal Service...
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=2561 sclass=netlink_route_socket pid=11622 comm=syz-executor.0
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=2561 sclass=netlink_route_socket pid=11628 comm=syz-executor.0
program syz-executor.1 is using a deprecated SCSI ioctl, please convert it to SG_IO
systemd-journald[11595]: File /var/log/journal/7e681e5076844de4a5cfa8606a84b008/system.journal corrupted or uncleanly shut down, renaming and replacing.
program syz-executor.1 is using a deprecated SCSI ioctl, please convert it to SG_IO
program syz-executor.1 is using a deprecated SCSI ioctl, please convert it to SG_IO
program syz-executor.1 is using a deprecated SCSI ioctl, please convert it to SG_IO
debugfs: Directory '201' with parent 'hci3' already present!
sysfs: cannot create duplicate filename '/devices/virtual/bluetooth/hci3/hci3:201'
CPU: 0 PID: 309 Comm: kworker/u5:3 Not tainted 5.19.0-next-20220812 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Workqueue: hci3 hci_rx_work
Call Trace:
dump_stack_lvl+0x8b/0xb3
sysfs_warn_dup.cold+0x1c/0x29
sysfs_create_dir_ns+0x237/0x290
kobject_add_internal+0x24c/0x8e0
kobject_add+0x150/0x1c0
device_add+0x35e/0x1ec0
hci_conn_add_sysfs+0x91/0x110
le_conn_complete_evt+0x117f/0x17d0
hci_le_conn_complete_evt+0x226/0x2c0
hci_le_meta_evt+0x2c0/0x4a0
hci_event_packet+0x636/0xf60
hci_rx_work+0xa82/0x1000
process_one_work+0xa0f/0x1690
worker_thread+0x637/0x1260
kthread+0x2ed/0x3a0
ret_from_fork+0x22/0x30
kobject_add_internal failed for hci3:201 with -EEXIST, don't try to register things with the same name in the same directory.
Bluetooth: hci3: failed to register connection device
debugfs: Directory '201' with parent 'hci3' already present!
sysfs: cannot create duplicate filename '/devices/virtual/bluetooth/hci3/hci3:201'
CPU: 0 PID: 309 Comm: kworker/u5:3 Not tainted 5.19.0-next-20220812 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Workqueue: hci3 hci_rx_work
Call Trace:
dump_stack_lvl+0x8b/0xb3
sysfs_warn_dup.cold+0x1c/0x29
sysfs_create_dir_ns+0x237/0x290
kobject_add_internal+0x24c/0x8e0
kobject_add+0x150/0x1c0
device_add+0x35e/0x1ec0
hci_conn_add_sysfs+0x91/0x110
le_conn_complete_evt+0x117f/0x17d0
hci_le_conn_complete_evt+0x226/0x2c0
hci_le_meta_evt+0x2c0/0x4a0
hci_event_packet+0x636/0xf60
hci_rx_work+0xa82/0x1000
process_one_work+0xa0f/0x1690
worker_thread+0x637/0x1260
kthread+0x2ed/0x3a0
ret_from_fork+0x22/0x30
kobject_add_internal failed for hci3:201 with -EEXIST, don't try to register things with the same name in the same directory.
Bluetooth: hci3: failed to register connection device
debugfs: Directory '201' with parent 'hci3' already present!
sysfs: cannot create duplicate filename '/devices/virtual/bluetooth/hci3/hci3:201'
CPU: 0 PID: 309 Comm: kworker/u5:3 Not tainted 5.19.0-next-20220812 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Workqueue: hci3 hci_rx_work
Call Trace:
dump_stack_lvl+0x8b/0xb3
sysfs_warn_dup.cold+0x1c/0x29
sysfs_create_dir_ns+0x237/0x290
kobject_add_internal+0x24c/0x8e0
kobject_add+0x150/0x1c0
device_add+0x35e/0x1ec0
hci_conn_add_sysfs+0x91/0x110
le_conn_complete_evt+0x117f/0x17d0
hci_le_conn_complete_evt+0x226/0x2c0
hci_le_meta_evt+0x2c0/0x4a0
hci_event_packet+0x636/0xf60
hci_rx_work+0xa82/0x1000
process_one_work+0xa0f/0x1690
worker_thread+0x637/0x1260
kthread+0x2ed/0x3a0
ret_from_fork+0x22/0x30
kobject_add_internal failed for hci3:201 with -EEXIST, don't try to register things with the same name in the same directory.
Bluetooth: hci3: failed to register connection device
debugfs: Directory '201' with parent 'hci3' already present!
sysfs: cannot create duplicate filename '/devices/virtual/bluetooth/hci3/hci3:201'
CPU: 0 PID: 309 Comm: kworker/u5:3 Not tainted 5.19.0-next-20220812 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Workqueue: hci3 hci_rx_work
Call Trace:
dump_stack_lvl+0x8b/0xb3
sysfs_warn_dup.cold+0x1c/0x29
sysfs_create_dir_ns+0x237/0x290
kobject_add_internal+0x24c/0x8e0
kobject_add+0x150/0x1c0
device_add+0x35e/0x1ec0
hci_conn_add_sysfs+0x91/0x110
le_conn_complete_evt+0x117f/0x17d0
hci_le_conn_complete_evt+0x226/0x2c0
hci_le_meta_evt+0x2c0/0x4a0
hci_event_packet+0x636/0xf60
hci_rx_work+0xa82/0x1000
process_one_work+0xa0f/0x1690
worker_thread+0x637/0x1260
kthread+0x2ed/0x3a0
ret_from_fork+0x22/0x30
kobject_add_internal failed for hci3:201 with -EEXIST, don't try to register things with the same name in the same directory.
Bluetooth: hci3: failed to register connection device
debugfs: Directory '201' with parent 'hci3' already present!
sysfs: cannot create duplicate filename '/devices/virtual/bluetooth/hci3/hci3:201'
CPU: 0 PID: 309 Comm: kworker/u5:3 Not tainted 5.19.0-next-20220812 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Workqueue: hci3 hci_rx_work
Call Trace:
dump_stack_lvl+0x8b/0xb3
sysfs_warn_dup.cold+0x1c/0x29
sysfs_create_dir_ns+0x237/0x290
kobject_add_internal+0x24c/0x8e0
kobject_add+0x150/0x1c0
device_add+0x35e/0x1ec0
hci_conn_add_sysfs+0x91/0x110
le_conn_complete_evt+0x117f/0x17d0
hci_le_conn_complete_evt+0x226/0x2c0
hci_le_meta_evt+0x2c0/0x4a0
hci_event_packet+0x636/0xf60
hci_rx_work+0xa82/0x1000
process_one_work+0xa0f/0x1690
worker_thread+0x637/0x1260
kthread+0x2ed/0x3a0
ret_from_fork+0x22/0x30
kobject_add_internal failed for hci3:201 with -EEXIST, don't try to register things with the same name in the same directory.
Bluetooth: hci3: failed to register connection device
systemd[1]: systemd-rfkill.service: Succeeded.
tmpfs: Bad value for 'mpol'
tmpfs: Bad value for 'mpol'
systemd[1]: Started Journal Service.
systemd-journald[11595]: Received client request to flush runtime journal.
netlink: 4 bytes leftover after parsing attributes in process `syz-executor.3'.