From: Viacheslav Dubeyko <slava@dubeyko.com>
To: 1sh1ro <yangguikun19@qq.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
Subject: Re: [PATCH v2 2/2] hfs: refuse catalog records that address the reserved B-tree CNIDs
Date: Mon, 12 Oct 2026 14:30:30 -0700 [thread overview]
Message-ID: <abe509bc80fe0f4e83f49af87aaa74fb95888aff.camel@dubeyko.com> (raw)
In-Reply-To: <tencent_5E46DC9CA04DCFA2DE7C8AA3C8532FBE1709@qq.com>
On Mon, 2026-10-12 at 15:44 +0800, 1sh1ro wrote:
> The extent and catalog B-tree inodes are described by the MDB, not by
> catalog records, but they are hashed by CNID like any other inode and
> hfs_test_inode() compares i_ino only. A crafted image with a catalog
> record whose FlNum (or DirID) is HFS_EXT_CNID or HFS_CAT_CNID
> therefore
> makes hfs_lookup() hand out the internal B-tree inode as a regular
> dentry,
> bypassing the CNID validation that hfs_read_inode() performs: a read
> exposes the B-tree file's contents, and a write would go through
> hfs_write_inode(), which tries to update a catalog record that does
> not
> exist.
>
> Refuse such records in hfs_iget() by returning NULL for the reserved
> B-tree CNIDs. hfs_lookup() reports that as -EACCES and
> hfs_fill_super() as a mount failure, the same as for any other
> unaddressable record.
>
> This is hardening on top of the file-type fix, not required for the
> panic; it can be dropped if hfs_is_valid_cnid()'s acceptance of
> HFS_CDR_FIL records for CNID 3/4 is intentional.
Please, combine both patches into one. First patch doesn't fix the
issue alone.
>
> Signed-off-by: 1sh1ro <yangguikun19@qq.com>
Please, provide the real name.
> ---
> fs/hfs/inode.c | 11 +++++++++++
> 1 file changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/fs/hfs/inode.c b/fs/hfs/inode.c
> index 4316d75..5190856 100644
> --- a/fs/hfs/inode.c
> +++ b/fs/hfs/inode.c
> @@ -520,6 +520,17 @@ struct inode *hfs_iget(struct super_block *sb,
> struct hfs_cat_key *key, hfs_cat_
> default:
> return NULL;
> }
> +
> + /*
> + * Never let a catalog record address one of the internal B-
> tree
> + * objects. hfs_test_inode() matches on i_ino alone, so
> such a
> + * record would make hfs_lookup() hand out the cached B-tree
> inode as
> + * a regular dentry, bypassing the CNID validation done by
> + * hfs_read_inode().
> + */
Please, rework or remove the comment. Currently, it's long and not
informative.
> + if (cnid == HFS_EXT_CNID || cnid == HFS_CAT_CNID)
I think we can reject all cnid that lower than HFS_FIRSTUSER_CNID.
Thanks,
Slava.
> + return NULL;
> +
> inode = iget5_locked(sb, cnid, hfs_test_inode,
> hfs_read_inode, &data);
> if (inode && (inode_state_read_once(inode) & I_NEW))
> unlock_new_inode(inode);
next prev parent reply other threads:[~2026-10-12 21:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260916080000.0-hfs-fix@localhost>
2026-09-16 9:09 ` [PATCH 1/1] hfs: don't let internal B-tree inodes leak into the VFS open path 1sh1ro
2026-09-16 18:33 ` Viacheslav Dubeyko
[not found] ` <20261012154438.6396-1-yangguikun19@qq.com>
2026-10-12 7:44 ` [PATCH v2 1/2] hfs: create the internal B-tree inodes through the generic iget path 1sh1ro
2026-10-12 21:26 ` Viacheslav Dubeyko
2026-10-12 7:44 ` [PATCH v2 2/2] hfs: refuse catalog records that address the reserved B-tree CNIDs 1sh1ro
2026-10-12 21:30 ` Viacheslav Dubeyko [this message]
2026-10-13 6:44 ` [PATCH v3] hfs: give the internal B-tree inodes a type and keep catalog records off them yangguikun
2026-10-13 21:38 ` Viacheslav Dubeyko
2026-10-14 8:03 ` [PATCH v4] hfs: initialize B-tree inodes and validate catalog CNIDs yangguikun
2026-10-14 22:27 ` Viacheslav Dubeyko
2026-10-15 7:06 ` [PATCH v5] " yangguikun
2026-10-12 7:44 ` [PATCH v2 0/2] hfs: keep the internal B-tree inodes out of the VFS open path 1sh1ro
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=abe509bc80fe0f4e83f49af87aaa74fb95888aff.camel@dubeyko.com \
--to=slava@dubeyko.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=yangguikun19@qq.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®