[syzbot] [bcachefs?] WARNING in __bch2_increment_clock

[syzbot] [bcachefs?] WARNING in __bch2_increment_clock

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    ee5b455b0ada Merge tag 'slab-for-6.9-rc7-fixes' of git://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=177a6698980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7144b4fe7fbf5900
dashboard link: https://syzkaller.appspot.com/bug?extid=e2edd0ba80d9b4a3ae8b
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-ee5b455b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/96e27f6a83fe/vmlinux-ee5b455b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/49d89ce985f7/bzImage-ee5b455b.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e2edd0ba80d9b4a3ae8b@syzkaller.appspotmail.com

------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 3 PID: 10086 at kernel/locking/lockdep.c:4643 mark_lock+0x590/0xc60 kernel/locking/lockdep.c:4643
Modules linked in:
CPU: 3 PID: 10086 Comm: kworker/3:2H Not tainted 6.9.0-rc7-syzkaller-00008-gee5b455b0ada #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: bcachefs_copygc bch2_write_point_do_index_updates
RIP: 0010:mark_lock+0x590/0xc60 kernel/locking/lockdep.c:4643
Code: 4c 89 ea 48 89 d9 4c 89 e7 e8 4c d5 ff ff 31 d2 e9 6b fb ff ff 90 48 c7 c6 40 b2 0c 8b 48 c7 c7 e0 ac 0c 8b e8 91 93 e4 ff 90 <0f> 0b 90 90 e9 5f fc ff ff e8 b2 67 ff ff ba 01 00 00 00 e9 3e fb
RSP: 0018:ffffc90003f56e00 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffffff81503039
RDX: ffff88804dc72440 RSI: ffffffff81503046 RDI: 0000000000000001
RBP: ffffc90003f56f40 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 000000002d2d2d2d R12: ffff88804de28000
R13: ffffc90003d378b0 R14: 000000004dc72440 R15: 1ffff920007eadc6
FS:  0000000000000000(0000) GS:ffff88806b500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2df66000 CR3: 00000000427cc000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __bch2_increment_clock+0x3b8/0x4a0 fs/bcachefs/clock.c:152
 bch2_increment_clock fs/bcachefs/clock.h:19 [inline]
 bch2_btree_node_alloc+0xce3/0xed0 fs/bcachefs/btree_update_interior.c:426
 bch2_btree_node_alloc_replacement+0xbb/0xd20 fs/bcachefs/btree_update_interior.c:447
 btree_split+0x1459/0x2b00 fs/bcachefs/btree_update_interior.c:1661
 bch2_btree_split_leaf+0x10c/0x6b0 fs/bcachefs/btree_update_interior.c:1856
 bch2_trans_commit_error+0x327/0xd00 fs/bcachefs/btree_trans_commit.c:896
 __bch2_trans_commit+0x3055/0x7880 fs/bcachefs/btree_trans_commit.c:1112
 bch2_trans_commit fs/bcachefs/btree_update.h:168 [inline]
 __bch2_data_update_index_update+0x3405/0x3cf0 fs/bcachefs/data_update.c:292
 bch2_data_update_index_update+0x5a/0x90 fs/bcachefs/data_update.c:338
 __bch2_write_index+0x17d/0xa60 fs/bcachefs/io_write.c:521
 bch2_write_point_do_index_updates+0x250/0x630 fs/bcachefs/io_write.c:629
 process_one_work+0x9a9/0x1ac0 kernel/workqueue.c:3267
 process_scheduled_works kernel/workqueue.c:3348 [inline]
 worker_thread+0x6c8/0xf70 kernel/workqueue.c:3429
 kthread+0x2c1/0x3a0 kernel/kthread.c:388
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup