syzbot


WARNING in hfsplus_ext_write_extent (2)

Status: auto-obsoleted due to no activity on 2024/03/29 06:17
Subsystems: hfs
[Documentation on labels]
Reported-by: syzbot+03628e5994f8f09f5455@syzkaller.appspotmail.com
First crash: 294d, last: 294d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [hfs?] WARNING in hfsplus_ext_write_extent (2) 0 (1) 2023/12/22 00:59
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING in hfsplus_ext_write_extent hfs 26 421d 680d 0/28 auto-obsoleted due to no activity on 2023/11/22 16:42
linux-6.1 WARNING in hfsplus_ext_write_extent 1 528d 528d 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: 6540 at kernel/locking/mutex.c:582 __mutex_lock_common kernel/locking/mutex.c:582 [inline]
WARNING: CPU: 1 PID: 6540 at kernel/locking/mutex.c:582 __mutex_lock+0xc36/0xd60 kernel/locking/mutex.c:747
Modules linked in:
CPU: 1 PID: 6540 Comm: kworker/u4:0 Not tainted 6.7.0-rc6-syzkaller-00022-g55cb5f43689d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: writeback wb_workfn (flush-7:4)
RIP: 0010:__mutex_lock_common kernel/locking/mutex.c:582 [inline]
RIP: 0010:__mutex_lock+0xc36/0xd60 kernel/locking/mutex.c:747
Code: 0f b6 04 20 84 c0 0f 85 18 01 00 00 83 3d 21 0c e0 03 00 75 19 90 48 c7 c7 60 90 6a 8b 48 c7 c6 00 91 6a 8b e8 1b 76 33 f6 90 <0f> 0b 90 90 90 e9 c8 f4 ff ff 90 0f 0b 90 e9 d6 f8 ff ff 90 0f 0b
RSP: 0018:ffffc90016a7f200 EFLAGS: 00010246
RAX: e1774778be1ec900 RBX: 0000000000000000 RCX: ffff888069518000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90016a7f350 R08: ffffffff81545d22 R09: 1ffff11017325172
R10: dffffc0000000000 R11: ffffed1017325173 R12: dffffc0000000000
R13: ffff8880355356a0 R14: 0000000000000000 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b3992d6000 CR3: 0000000032017000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 hfsplus_ext_write_extent+0x8e/0x1f0 fs/hfsplus/extents.c:149
 hfsplus_write_inode+0x22/0x5e0 fs/hfsplus/super.c:154
 write_inode fs/fs-writeback.c:1473 [inline]
 __writeback_single_inode+0x69b/0xfc0 fs/fs-writeback.c:1690
 writeback_sb_inodes+0x8e3/0x1220 fs/fs-writeback.c:1916
 wb_writeback+0x44d/0xc70 fs/fs-writeback.c:2092
 wb_do_writeback fs/fs-writeback.c:2239 [inline]
 wb_workfn+0x400/0xfb0 fs/fs-writeback.c:2279
 process_one_work kernel/workqueue.c:2627 [inline]
 process_scheduled_works+0x90f/0x1420 kernel/workqueue.c:2700
 worker_thread+0xa5f/0x1000 kernel/workqueue.c:2781
 kthread+0x2d3/0x370 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/12/20 06:17 upstream 55cb5f43689d 3ad490ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in hfsplus_ext_write_extent
* Struck through repros no longer work on HEAD.