[syzbot] [hfs?] WARNING in check_flush_dependency (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c72692105976 Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=150cf0cc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3074fa928809af2b
dashboard link: https://syzkaller.appspot.com/bug?extid=09455b3f0a89d685a9d3
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/02d65c9d9776/disk-c7269210.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/caf24085c451/vmlinux-c7269210.xz
kernel image: https://storage.googleapis.com/syzbot-assets/92025d8a23a1/Image-c7269210.gz.xz

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

------------[ cut here ]------------
workqueue: WQ_MEM_RECLAIM dio/loop0:dio_aio_complete_work is flushing !WQ_MEM_RECLAIM events_long:flush_mdb
WARNING: CPU: 1 PID: 6522 at kernel/workqueue.c:3721 check_flush_dependency+0x290/0x344 kernel/workqueue.c:3717
Modules linked in:
CPU: 1 UID: 0 PID: 6522 Comm: kworker/1:5 Not tainted 6.15.0-rc2-syzkaller-gc72692105976 #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: dio/loop0 dio_aio_complete_work
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : check_flush_dependency+0x290/0x344 kernel/workqueue.c:3717
lr : check_flush_dependency+0x290/0x344 kernel/workqueue.c:3717
sp : ffff8000a4cc76d0
x29: ffff8000a4cc76d0 x28: 0000000000000000 x27: 1fffe0001dc7b42b
x26: 0000000000000000 x25: ffff80009341b000 x24: ffff0000d23f4400
x23: dfff800000000000 x22: ffff0000d3fb1918 x21: ffff80008133b000
x20: ffff0000d23f4578 x19: ffff0000c0029400 x18: 0000000000000008
x17: 00000000fffffffa x16: ffff80008333704c x15: 0000000000000001
x14: 1fffe000366e2322 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000000003 x10: 0000000000ff0100 x9 : a994bece50049800
x8 : a994bece50049800 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff8000a4cc6e58 x4 : ffff800090035460 x3 : ffff800080750da0
x2 : 0000000000000001 x1 : 0000000100000001 x0 : 0000000000000000
Call trace:
check_flush_dependency+0x290/0x344 kernel/workqueue.c:3717 (P)
start_flush_work kernel/workqueue.c:4171 [inline]
__flush_work+0x220/0x958 kernel/workqueue.c:4208
flush_work kernel/workqueue.c:4265 [inline]
flush_delayed_work+0xcc/0xf8 kernel/workqueue.c:4287
hfs_file_fsync+0xec/0x148 fs/hfs/inode.c:680
vfs_fsync_range+0x160/0x19c fs/sync.c:187
generic_write_sync include/linux/fs.h:2976 [inline]
dio_complete+0x510/0x6bc fs/direct-io.c:313
dio_aio_complete_work+0x28/0x38 fs/direct-io.c:325
process_one_work+0x810/0x1638 kernel/workqueue.c:3238
process_scheduled_works kernel/workqueue.c:3319 [inline]
worker_thread+0x97c/0xf08 kernel/workqueue.c:3400
kthread+0x674/0x7dc kernel/kthread.c:464
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862
irq event stamp: 11908
hardirqs last enabled at (11907): [<ffff800080371ff0>] flush_delayed_work+0xac/0xf8 kernel/workqueue.c:4286
hardirqs last disabled at (11908): [<ffff80008b9be494>] __raw_spin_lock_irq include/linux/spinlock_api_smp.h:117 [inline]
hardirqs last disabled at (11908): [<ffff80008b9be494>] _raw_spin_lock_irq+0x28/0x70 kernel/locking/spinlock.c:170
softirqs last enabled at (11276): [<ffff80008583fac0>] spin_unlock_bh include/linux/spinlock.h:396 [inline]
softirqs last enabled at (11276): [<ffff80008583fac0>] ptr_ring_consume_bh include/linux/ptr_ring.h:367 [inline]
softirqs last enabled at (11276): [<ffff80008583fac0>] wg_packet_encrypt_worker+0x121c/0x12ac drivers/net/wireguard/send.c:293
softirqs last disabled at (11274): [<ffff80008583f874>] spin_lock_bh include/linux/spinlock.h:356 [inline]
softirqs last disabled at (11274): [<ffff80008583f874>] ptr_ring_consume_bh include/linux/ptr_ring.h:365 [inline]
softirqs last disabled at (11274): [<ffff80008583f874>] wg_packet_encrypt_worker+0xfd0/0x12ac drivers/net/wireguard/send.c:293
---[ end trace 0000000000000000 ]---


---
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 syzk...@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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: e0f4c8dd9d2d Merge branch 'for-next/core' into for-kernelci

git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci

console output: https://syzkaller.appspot.com/x/log.txt?x=107e84f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=868079b7b8989c3c
dashboard link: https://syzkaller.appspot.com/bug?extid=09455b3f0a89d685a9d3
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=166538f4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1028339b980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/463c704c2ee6/disk-e0f4c8dd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1bb99dd967d9/vmlinux-e0f4c8dd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/505fe552b9a8/Image-e0f4c8dd.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9018fb7fad71/mount_0.gz

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

------------[ cut here ]------------
workqueue: WQ_MEM_RECLAIM dio/loop0:dio_aio_complete_work is flushing !WQ_MEM_RECLAIM events_long:flush_mdb

WARNING: CPU: 1 PID: 1786 at kernel/workqueue.c:3721 check_flush_dependency+0x288/0x33c kernel/workqueue.c:3717
Modules linked in:
CPU: 1 UID: 0 PID: 1786 Comm: kworker/1:2 Not tainted 6.15.0-rc4-syzkaller-ge0f4c8dd9d2d #0 PREEMPT

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: dio/loop0 dio_aio_complete_work
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)

pc : check_flush_dependency+0x288/0x33c kernel/workqueue.c:3717
lr : check_flush_dependency+0x288/0x33c kernel/workqueue.c:3717
sp : ffff80009f0f7730
x29: ffff80009f0f7740 x28: dfff800000000000 x27: ffff700013e1eef4
x26: ffff0000c1081408 x25: 0000000000000000 x24: ffff0000d7e64000
x23: dfff800000000000 x22: ffff8000812ac698 x21: ffff800092804000
x20: ffff0000cae4c218 x19: ffff0000c0029400 x18: 00000000ffffffff
x17: ffff800092f13000 x16: ffff80008ada5d6c x15: 0000000000000001
x14: 1fffe00036711ae2 x13: 0000000000000000 x12: 0000000000000000
x11: ffff600036711ae3 x10: 0000000000ff0100 x9 : 88d2378845d08000
x8 : 88d2378845d08000 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80009f0f7078 x4 : ffff80008f3f4fa0 x3 : ffff8000807ab99c

x2 : 0000000000000001 x1 : 0000000100000001 x0 : 0000000000000000
Call trace:

check_flush_dependency+0x288/0x33c kernel/workqueue.c:3717 (P)
start_flush_work kernel/workqueue.c:4171 [inline]
__flush_work+0x220/0x8c0 kernel/workqueue.c:4208

flush_work kernel/workqueue.c:4265 [inline]
flush_delayed_work+0xcc/0xf8 kernel/workqueue.c:4287

hfs_file_fsync+0xe8/0x144 fs/hfs/inode.c:680

vfs_fsync_range+0x160/0x19c fs/sync.c:187
generic_write_sync include/linux/fs.h:2976 [inline]
dio_complete+0x510/0x6bc fs/direct-io.c:313
dio_aio_complete_work+0x28/0x38 fs/direct-io.c:325

process_one_work+0x7e8/0x156c kernel/workqueue.c:3238
process_scheduled_works kernel/workqueue.c:3319 [inline]
worker_thread+0x958/0xed8 kernel/workqueue.c:3400
kthread+0x5fc/0x75c kernel/kthread.c:464
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862
irq event stamp: 27154
hardirqs last enabled at (27153): [<ffff800080415058>] flush_delayed_work+0xac/0xf8 kernel/workqueue.c:4286
hardirqs last disabled at (27154): [<ffff80008adc663c>] __raw_spin_lock_irq include/linux/spinlock_api_smp.h:117 [inline]
hardirqs last disabled at (27154): [<ffff80008adc663c>] _raw_spin_lock_irq+0x28/0x70 kernel/locking/spinlock.c:170
softirqs last enabled at (27092): [<ffff80008978635c>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (27090): [<ffff800089786328>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19

---[ end trace 0000000000000000 ]---


---

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.