All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d395b0c369e492a17530@syzkaller.appspotmail.com>
To: gianf.trad@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] KMSAN: uninit-value in __hfs_ext_cache_extent (2)
Date: Tue, 22 Oct 2024 08:52:04 -0700	[thread overview]
Message-ID: <6717ca24.050a0220.10f4f4.0150.GAE@google.com> (raw)
In-Reply-To: <3b0be684-0b50-4151-a275-0751715d1be8@gmail.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in hfs_write_inode

------------[ cut here ]------------
kernel BUG at fs/hfs/inode.c:444!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI
CPU: 0 UID: 0 PID: 4551 Comm: kworker/u8:26 Not tainted 6.12.0-rc4-syzkaller-gc2ee9f594da8-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: writeback wb_workfn (flush-7:0)
RIP: 0010:hfs_write_inode+0xe81/0xe90 fs/hfs/inode.c:444
Code: e9 f4 fd ff ff 8b 3a e8 dd 6c 31 ff e9 02 fe ff ff 49 89 d6 8b 7d c8 e8 8d 68 31 ff 41 89 06 e9 26 fe ff ff e8 30 73 98 fe 90 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 90 90 90 90 90 90 90
RSP: 0018:ffff888115ccb5c0 EFLAGS: 00010293
RAX: ffffffff831c8500 RBX: 0000000000000000 RCX: ffff8881151c8000
RDX: 0000000000000000 RSI: ffffffff91870ec0 RDI: 0000000000000000
RBP: ffff888115ccb6a8 R08: 0000000000000007 R09: ffffffff831c77bc
R10: 0000000000000003 R11: ffff8881151c8000 R12: 0000000000000000
R13: 0000000000000000 R14: ffff888012a7ca70 R15: ffff8881151c8b38
FS:  0000000000000000(0000) GS:ffff88813fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcdb4e446a8 CR3: 000000004484a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 write_inode fs/fs-writeback.c:1503 [inline]
 __writeback_single_inode+0x8da/0x1290 fs/fs-writeback.c:1723
 writeback_sb_inodes+0xa34/0x1c20 fs/fs-writeback.c:1954
 wb_writeback+0x4df/0xcb0 fs/fs-writeback.c:2134
 wb_do_writeback fs/fs-writeback.c:2281 [inline]
 wb_workfn+0x40b/0x1940 fs/fs-writeback.c:2321
 process_one_work kernel/workqueue.c:3229 [inline]
 process_scheduled_works+0xae0/0x1c40 kernel/workqueue.c:3310
 worker_thread+0xea7/0x14f0 kernel/workqueue.c:3391
 kthread+0x3e2/0x540 kernel/kthread.c:389
 ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:hfs_write_inode+0xe81/0xe90 fs/hfs/inode.c:444
Code: e9 f4 fd ff ff 8b 3a e8 dd 6c 31 ff e9 02 fe ff ff 49 89 d6 8b 7d c8 e8 8d 68 31 ff 41 89 06 e9 26 fe ff ff e8 30 73 98 fe 90 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 90 90 90 90 90 90 90
RSP: 0018:ffff888115ccb5c0 EFLAGS: 00010293
RAX: ffffffff831c8500 RBX: 0000000000000000 RCX: ffff8881151c8000
RDX: 0000000000000000 RSI: ffffffff91870ec0 RDI: 0000000000000000
RBP: ffff888115ccb6a8 R08: 0000000000000007 R09: ffffffff831c77bc
R10: 0000000000000003 R11: ffff8881151c8000 R12: 0000000000000000
R13: 0000000000000000 R14: ffff888012a7ca70 R15: ffff8881151c8b38
FS:  0000000000000000(0000) GS:ffff88813fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcdb4e446a8 CR3: 000000004484a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


Tested on:

commit:         c2ee9f59 KVM: selftests: Fix build on on non-x86 archi..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14922640580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f0a45c444eedcbdb
dashboard link: https://syzkaller.appspot.com/bug?extid=d395b0c369e492a17530
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=164c4a5f980000


       reply	other threads:[~2024-10-22 15:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3b0be684-0b50-4151-a275-0751715d1be8@gmail.com>
2024-10-22 15:52 ` syzbot [this message]
2024-10-22 17:05   ` [syzbot] [hfs?] KMSAN: uninit-value in __hfs_ext_cache_extent (2) Gianfranco Trad
2024-10-22 17:31     ` syzbot
     [not found] <d703694c-a0a7-480b-bafa-c8703306d2f5@gmail.com>
2024-11-13  0:26 ` syzbot
     [not found] <9be1baa3-d2f4-4e20-9f13-c6c12f0813dc@gmail.com>
2024-11-11 21:10 ` syzbot
     [not found] <CAN=OONzCeRjbK6TbqenTyjYSpPh4f1-5UmrzeYcW2anq80P_EA@mail.gmail.com>
2024-11-06  6:52 ` syzbot
     [not found] <CAN=OONw=P_=3i7RSj67ZqW++8wcrmzuE-oN_fwjS7aR1t_B94g@mail.gmail.com>
2024-11-06  3:57 ` syzbot
     [not found] <CAN=OONwWNfETusinz2A7yGG2OFtS8Nnn8z9FhUTpPuugHKnMkw@mail.gmail.com>
2024-11-05 21:12 ` syzbot
     [not found] <CAN=OONzfDPeFZ-BnRd53psEUgv2-wLFxq299SLLK9UqG_iZ4NA@mail.gmail.com>
2024-11-05 10:25 ` syzbot
     [not found] <CAHiZj8j_3jKyqB=_KB9ctK_hYu_gS6nn0VtDokTrnJ=4P9OGWw@mail.gmail.com>
2024-10-02  7:34 ` syzbot
     [not found] <CAHiZj8gaK1pvOZzxndtb8KTCMoj=UczhHv6_f6ogbMtOU7HdPQ@mail.gmail.com>
2024-10-01 22:35 ` syzbot
2024-10-01  9:27 syzbot
2024-10-10 13:41 ` Qianqiang Liu
2024-10-10 14:16   ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6717ca24.050a0220.10f4f4.0150.GAE@google.com \
    --to=syzbot+d395b0c369e492a17530@syzkaller.appspotmail.com \
    --cc=gianf.trad@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.