From: syzbot <syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] memory leak in __hfs_bnode_create
Date: Thu, 16 Apr 2026 23:12:01 -0700 [thread overview]
Message-ID: <69e1cf31.050a0220.1de265.0003.GAE@google.com> (raw)
In-Reply-To: <tencent_98E8C6ED26CD98795E6DF02DA16F0897780A@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.com
Tested-by: syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.com
Tested on:
commit: 43cfbdda Merge tag 'for-linus-iommufd' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d441ba580000
kernel config: https://syzkaller.appspot.com/x/.config?x=208b81ceb4623b6b
dashboard link: https://syzkaller.appspot.com/bug?extid=98547b0428b6a6a3467c
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=173fc4ce580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-04-17 6:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 1:56 [syzbot] [hfs?] memory leak in __hfs_bnode_create syzbot
2026-04-17 3:11 ` Edward Adam Davis
2026-04-17 5:52 ` syzbot
2026-04-17 4:52 ` Edward Adam Davis
2026-04-17 6:12 ` syzbot [this message]
2026-04-17 5:04 ` Edward Adam Davis
2026-04-17 6:23 ` syzbot
2026-04-17 6:05 ` Edward Adam Davis
2026-04-17 6:47 ` syzbot
2026-04-17 6:22 ` Edward Adam Davis
2026-04-17 6:58 ` syzbot
2026-04-17 6:58 ` [PATCH] hfsplus: Supports freeing newly created tree head Edward Adam Davis
2026-04-17 22:03 ` Viacheslav Dubeyko
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=69e1cf31.050a0220.1de265.0003.GAE@google.com \
--to=syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.com \
--cc=eadavis@qq.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox