WARNING in hfsplus_ext_write_extent

Status: auto-obsoleted due to no activity on 2026/05/28 04:43
Reported-by: syzbot+1e9e06cbbf68757b56a3@syzkaller.appspotmail.com
First crash: 188d, last: 164d
▶ ▼ Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING in hfsplus_ext_write_extent (2) hfs -1 1 954d 952d 0/29 auto-obsoleted due to no activity on 2024/03/29 06:17
linux-6.1 WARNING in hfsplus_ext_write_extent (2) -1 1 283d 283d 0/3 auto-obsoleted due to no activity on 2026/01/29 02:49
linux-5.15 WARNING in hfsplus_ext_write_extent -1 2 386d 396d 0/3 auto-obsoleted due to no activity on 2025/10/18 16:49
linux-5.15 WARNING in hfsplus_ext_write_extent (2) -1 1 254d 254d 0/3 auto-obsoleted due to no activity on 2026/02/27 18:16
upstream WARNING in hfsplus_ext_write_extent hfs -1 26 1082d 1341d 0/29 auto-obsoleted due to no activity on 2023/11/22 16:42
linux-6.1 WARNING in hfsplus_ext_write_extent -1 1 1188d 1188d 0/3 auto-obsoleted due to no activity on 2023/08/23 09:09

Sample crash report:
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 1 PID: 2920 at kernel/locking/mutex.c:582 __mutex_lock_common kernel/locking/mutex.c:582 [inline]
WARNING: CPU: 1 PID: 2920 at kernel/locking/mutex.c:582 __mutex_lock+0xb85/0xcc0 kernel/locking/mutex.c:747
Modules linked in:
CPU: 1 PID: 2920 Comm: kworker/u4:8 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Workqueue: writeback wb_workfn (flush-7:0)
RIP: 0010:__mutex_lock_common kernel/locking/mutex.c:582 [inline]
RIP: 0010:__mutex_lock+0xb85/0xcc0 kernel/locking/mutex.c:747
Code: 04 08 84 c0 0f 85 27 01 00 00 83 3d 54 0b fe 03 00 0f 85 95 f5 ff ff 48 c7 c7 a0 b3 ca 8a 48 c7 c6 40 b4 ca 8a e8 ab cf c3 f6 <0f> 0b e9 7b f5 ff ff 0f 0b e9 5f f9 ff ff 0f 0b e9 18 f6 ff ff e8
RSP: 0018:ffffc9000c17f220 EFLAGS: 00010246
RAX: 87c15579ac575600 RBX: ffff888058549460 RCX: ffff88802bcd3c00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffc9000c17f370 R08: ffff8880b8f28c13 R09: 1ffff110171e5182
R10: dffffc0000000000 R11: ffffed10171e5183 R12: 0000000000000000
R13: 1ffff9200182fe54 R14: dffffc0000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffc4049bd8 CR3: 0000000019ab0000 CR4: 00000000003506e0
Call Trace:
 <TASK>
 hfsplus_ext_write_extent+0x91/0x230 fs/hfsplus/extents.c:149
 hfsplus_write_inode+0x22/0x5e0 fs/hfsplus/super.c:167
 write_inode fs/fs-writeback.c:1483 [inline]
 __writeback_single_inode+0x705/0xec0 fs/fs-writeback.c:1700
 writeback_sb_inodes+0x7cd/0xf50 fs/fs-writeback.c:1926
 wb_writeback+0x46a/0xbf0 fs/fs-writeback.c:2105
 wb_do_writeback fs/fs-writeback.c:2252 [inline]
 wb_workfn+0x400/0xe60 fs/fs-writeback.c:2292
 process_one_work kernel/workqueue.c:2634 [inline]
 process_scheduled_works+0xa5d/0x15d0 kernel/workqueue.c:2711
 worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/02/17 04:42 linux-6.6.y 56865d9b7074 e439b951 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan WARNING in hfsplus_ext_write_extent
2026/01/28 11:14 linux-6.6.y cbb31f77b879 004c195c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan WARNING in hfsplus_ext_write_extent
2026/01/23 22:02 linux-6.6.y cbb31f77b879 4f25b9b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan WARNING in hfsplus_ext_write_extent
* Struck through repros no longer work on HEAD.