From: syzbot <syzbot+97e301b4b82ae803d21b@syzkaller.appspotmail.com>
To: contact@gvernon.com, damien.lemoal@opensource.wdc.com,
jlayton@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] [hfs?] kernel BUG in hfs_write_inode
Date: Thu, 02 Oct 2025 18:27:02 -0700 [thread overview]
Message-ID: <68df2666.050a0220.2c17c1.000e.GAE@google.com> (raw)
In-Reply-To: <aN8g1OkBMndiyKyd@Bertha>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+97e301b4b82ae803d21b@syzkaller.appspotmail.com
Tested-by: syzbot+97e301b4b82ae803d21b@syzkaller.appspotmail.com
Tested on:
commit: 24d9e8b3 Merge tag 'slab-for-6.18' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1472aa7c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e9442f6915cec8b7
dashboard link: https://syzkaller.appspot.com/bug?extid=97e301b4b82ae803d21b
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=13c8d942580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-10-03 1:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 9:45 [syzbot] kernel BUG in hfs_write_inode syzbot
2025-10-02 16:16 ` George Anthony Vernon
2025-10-02 16:31 ` [syzbot] [hfs?] " syzbot
2025-10-02 23:55 ` George Anthony Vernon
2025-10-03 0:18 ` syzbot
2025-10-03 1:03 ` George Anthony Vernon
2025-10-03 1:27 ` syzbot [this message]
2025-10-29 2:49 ` Forwarded: " syzbot
2026-03-09 23:04 ` Forwarded: syzbot
2026-03-11 20:48 ` Forwarded: Re: [syzbot] [hfs?] kernel BUG in hfs_write_inode syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-11-23 11:55 Tetsuo Handa
2024-11-23 12:32 ` [syzbot] [hfs?] " syzbot
[not found] <aQGALTpEwjtSrAJD@Bertha>
2025-10-29 2:47 ` syzbot
[not found] <aQGA0rVKnoH3PDXh@Bertha>
2025-10-29 4:00 ` syzbot
[not found] <aa9SERLWzDdfA9Ih@Bertha>
2026-03-09 23:28 ` syzbot
[not found] <abHVInyhvToCSWjV@Bertha>
2026-03-11 21:11 ` 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=68df2666.050a0220.2c17c1.000e.GAE@google.com \
--to=syzbot+97e301b4b82ae803d21b@syzkaller.appspotmail.com \
--cc=contact@gvernon.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox