From: Song jeonghak <thdwjdgkr123@gmail.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Yangtao Li <frank.li@vivo.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Mahmut Emin Kurhan <guvenlik@noroxi.com>,
Shardul Bankar <shardul.b@mpiricsoftware.com>,
Edward Adam Davis <eadavis@qq.com>,
Markus Elfring <Markus.Elfring@web.de>,
syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] hfsplus: free failed b-tree nodes in hfs_bnode_put()
Date: Wed, 4 Nov 2026 11:18:42 +0900 [thread overview]
Message-ID: <20261104021842.18650-1-thdwjdgkr123@gmail.com> (raw)
In-Reply-To: <c05f958a83de97e38c2e54bb67ba3478ffd471e1.camel@dubeyko.com>
Hi Slava,
> I've accepted this patchset [1] recently with some modifications on my
> side. I assume that it has fixed the issue already. Am I wrong?
You are right, it fixes the issue. I missed that patchset: it was not
sent to syzbot, so it is not listed on the syzbot page, and that was
where I looked for earlier fixes. Sorry for the noise.
To be sure, I applied ed8b389cf5e1 ("hfsplus: fix B-tree node leak on
hfs_btree_open() error path") from your for-next branch on top of
next-20261023 and ran the syzbot C reproducer in QEMU (x86_64, kmemleak):
next-20261023: leak reported in 1 of 1 runs
next-20261023 + ed8b389cf5e1: no leak in 3 of 3 runs, two of which
ran with slub_debug=FZPU
Please drop my patch.
That commit has no Reported-by or Closes tag, so syzbot will keep this
report open. If you can still amend it, could you add these?
Reported-by: syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=98547b0428b6a6a3467c
Otherwise I can send a "#syz fix:" command once the commit is in
linux-next.
Tested-by: Song jeonghak <thdwjdgkr123@gmail.com>
Regards,
Song jeonghak
prev parent reply other threads:[~2026-11-04 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 2:25 Song jeonghak
2026-11-03 8:19 ` Markus Elfring
2026-11-03 19:44 ` Viacheslav Dubeyko
2026-11-04 2:18 ` Song jeonghak [this message]
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=20261104021842.18650-1-thdwjdgkr123@gmail.com \
--to=thdwjdgkr123@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=eadavis@qq.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=guvenlik@noroxi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shardul.b@mpiricsoftware.com \
--cc=slava@dubeyko.com \
--cc=syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®