From: Viacheslav Dubeyko <vdubeyko@redhat.com>
To: Edward Adam Davis <eadavis@qq.com>,
syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.com
Cc: frank.li@vivo.com, glaubitz@physik.fu-berlin.de,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
slava@dubeyko.com, syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] hfsplus: Supports freeing newly created tree head
Date: Fri, 17 Apr 2026 15:03:17 -0700 [thread overview]
Message-ID: <60605973b66496b04c6847ceb6fa46dfada6a628.camel@redhat.com> (raw)
In-Reply-To: <tencent_C4F16CD096B0EAEAEE5ACDB07A266E382C0A@qq.com>
On Fri, 2026-04-17 at 14:58 +0800, Edward Adam Davis wrote:
> hfs_bnode_put() does not support deallocating a newly created btree
> head node; therefore, regardless of whether hfsplus_bnode_find() succeeds
> or fails, it cannot effectively reclaim the memory allocated for a newly
> created head node.
>
> When finding a head node, if the node is a newly created one, we can use
> hfs_bnode_free() to reclaim its memory.
>
> [1]
> BUG: memory leak
> unreferenced object 0xffff88811cabc840 (size 96):
> backtrace (crc 3e2dadb7):
> __hfs_bnode_create+0x59/0x310 fs/hfsplus/bnode.c:469
> hfsplus_bnode_find+0x13e/0x580 fs/hfsplus/bnode.c:547
> hfsplus_btree_open+0x2fa/0x6d0 fs/hfsplus/btree.c:382
> hfsplus_fill_super+0x272/0x880 fs/hfsplus/super.c:548
I need slightly more detailed and clear explanation how the issue has been
happened and why we need to fix it in a such way. Currently, I don't have the
complete picture how this happened. I am sure that you have the complete
picture. :) Could you please share what you have in your mind? :) Don't hide the
wisdom. ;)
Thanks,
Slava.
>
> Fixes: 8ad2c6a36ac4 ("hfsplus: validate b-tree node 0 bitmap at mount time")
> Reported-by: syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=98547b0428b6a6a3467c
> Tested-by: syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.com
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
> ---
> fs/hfsplus/bnode.c | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/fs/hfsplus/bnode.c b/fs/hfsplus/bnode.c
> index f8b5a8ae58ff..65902104882a 100644
> --- a/fs/hfsplus/bnode.c
> +++ b/fs/hfsplus/bnode.c
> @@ -598,14 +598,18 @@ struct hfs_bnode *hfs_bnode_find(struct hfs_btree *tree, u32 num)
> if (key_size >= entry_size || key_size & 1)
> goto node_error;
> }
> - clear_bit(HFS_BNODE_NEW, &node->flags);
> - wake_up(&node->lock_wq);
> + if (num != HFSPLUS_TREE_HEAD) {
> + clear_bit(HFS_BNODE_NEW, &node->flags);
> + wake_up(&node->lock_wq);
> + }
> return node;
>
> node_error:
> set_bit(HFS_BNODE_ERROR, &node->flags);
> - clear_bit(HFS_BNODE_NEW, &node->flags);
> - wake_up(&node->lock_wq);
> + if (num != HFSPLUS_TREE_HEAD) {
> + clear_bit(HFS_BNODE_NEW, &node->flags);
> + wake_up(&node->lock_wq);
> + }
> hfs_bnode_put(node);
> return ERR_PTR(-EIO);
> }
> @@ -694,6 +698,10 @@ void hfs_bnode_put(struct hfs_bnode *node)
> hfs_bnode_free(node);
> return;
> }
> + if (test_bit(HFS_BNODE_NEW, &node->flags)) {
> + hfs_bnode_unhash(node);
> + hfs_bnode_free(node);
> + }
> spin_unlock(&tree->hash_lock);
> }
> }
next prev parent reply other threads:[~2026-04-17 22:03 UTC|newest]
Thread overview: 16+ 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
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 [this message]
2026-04-18 9:37 ` Edward Adam Davis
2026-04-22 18:19 ` Viacheslav Dubeyko
2026-04-28 2:37 ` Edward Adam Davis
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=60605973b66496b04c6847ceb6fa46dfada6a628.camel@redhat.com \
--to=vdubeyko@redhat.com \
--cc=eadavis@qq.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.com \
--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
all inboxes | Powered by JetHome®