syzbot


WARNING in hfs_write_inode

Status: fixed on 2023/06/08 14:41
Subsystems: hfs
[Documentation on labels]
Reported-by: syzbot+7bb7cd3595533513a9e7@syzkaller.appspotmail.com
Fix commit: cb7a95af78d2 hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling
First crash: 510d, last: 508d
Cause bisection: introduced by (bisect log) :
commit 55d1cbbbb29e6656c662ee8f73ba1fc4777532eb
Author: Arnd Bergmann <arnd@arndb.de>
Date: Tue Nov 9 02:35:04 2021 +0000

  hfs/hfsplus: use WARN_ON for sanity check

Crash: WARNING in hfs_write_inode (log)
Repro: C syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [hfs?] WARNING in hfs_write_inode 33 (34) 2023/07/21 13:10

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 1 PID: 39 at fs/hfs/inode.c:489 hfs_write_inode+0x85d/0xb40
Modules linked in:
CPU: 1 PID: 39 Comm: kworker/u4:2 Not tainted 6.2.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: writeback wb_workfn (flush-7:0)
RIP: 0010:hfs_write_inode+0x85d/0xb40 fs/hfs/inode.c:489
Code: 0f 7e ff e9 fc f9 ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 4e fa ff ff 48 89 df e8 1d 0f 7e ff e9 41 fa ff ff e8 33 65 28 ff <0f> 0b e9 93 fd ff ff 89 d9 80 e1 07 38 c1 0f 8c f1 fa ff ff 48 89
RSP: 0018:ffffc90000b07340 EFLAGS: 00010293
RAX: ffffffff8263762d RBX: 0000000000000050 RCX: ffff888012a98000
RDX: 0000000000000000 RSI: 0000000000000050 RDI: 0000000000000066
RBP: ffffc90000b074d0 R08: ffffffff826373b9 R09: ffffed1002fa63c6
R10: ffffed1002fa63c6 R11: 1ffff11002fa63c4 R12: dffffc0000000000
R13: ffff888029558158 R14: ffffc90000b07380 R15: 1ffff92000160e6c
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f793d0e3140 CR3: 000000002865e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 write_inode fs/fs-writeback.c:1451 [inline]
 __writeback_single_inode+0x4d6/0x670 fs/fs-writeback.c:1663
 writeback_sb_inodes+0x812/0x1050 fs/fs-writeback.c:1889
 wb_writeback+0x41f/0x7b0 fs/fs-writeback.c:2063
 wb_do_writeback fs/fs-writeback.c:2206 [inline]
 wb_workfn+0x3cb/0xef0 fs/fs-writeback.c:2246
 process_one_work+0x877/0xdb0 kernel/workqueue.c:2289
 worker_thread+0xb14/0x1330 kernel/workqueue.c:2436
 kthread+0x266/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/02 17:09 upstream 88603b6dc419 ab32d508 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING in hfs_write_inode
2022/12/31 14:39 upstream c8451c141e07 ab32d508 .config strace log report syz C [mounted in repro] ci-upstream-kasan-gce-selinux-root WARNING in hfs_write_inode
2022/12/31 14:17 upstream c8451c141e07 ab32d508 .config console log report info ci-upstream-kasan-gce-selinux-root WARNING in hfs_write_inode
* Struck through repros no longer work on HEAD.