From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Hengyu Liang <hengyul@cs.unc.edu>
Cc: glaubitz@physik.fu-berlin.de, frank.li@vivo.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] hfsplus: preserve FinderInfo when listing extended attributes
Date: Thu, 22 Oct 2026 11:49:56 -0700 [thread overview]
Message-ID: <a5830eb2ef9f0dfd43a9cd1255caa3f9f77541f1.camel@dubeyko.com> (raw)
In-Reply-To: <20261022094058.1169039-1-hengyul@cs.unc.edu>
On Thu, 2026-10-22 at 05:40 -0400, Hengyu Liang wrote:
> Commit aef507847129 ("hfsplus: fix generic/062 xfstests failure")
> made
> hfsplus_listxattr() return zero when the inode has no records in the
> attributes B-tree.
>
> However, osx.com.apple.FinderInfo is stored in the catalog record,
> and
> hfsplus_listxattr() has already added it to the result at that point.
> Setting the result to zero drops it. As of now, a file whose only
> extended attribute is FinderInfo gets an empty list on a volume with
> an attributes B-tree, which mkfs.hfsplus creates by default.
> getxattr()
> still returns the value.
>
> The issue can be reproduced with:
>
> truncate -s 64M hfs.img
> mkfs.hfsplus hfs.img
> mount -o loop hfs.img /mnt
> touch /mnt/file
> v=0x54455854$(printf %056d 0)
> setfattr -n osx.com.apple.FinderInfo -v $v /mnt/file
> getfattr -m - /mnt/file
>
> Without this patch, getfattr prints nothing. With this patch, it
> lists
> the FinderInfo entry.
>
> This patch keeps the result of hfsplus_listxattr_finder_info() when
> no
> attributes B-tree records are found, as is already done when the
> volume has no attributes B-tree. A file without extended attributes
> still gets an empty list.
>
> Fixes: aef507847129 ("hfsplus: fix generic/062 xfstests failure")
> Cc: stable@vger.kernel.org
> Signed-off-by: Hengyu Liang <hengyul@cs.unc.edu>
> ---
> Changes in v2:
> - Restructure the error check as suggested by Viacheslav Dubeyko. No
> functional change.
> - v1:
> https://lore.kernel.org/r/20261021174534.482192-1-hengyul@cs.unc.edu
>
> Tested in KVM with KASAN on a804c5742bff, without and with this
> patch:
> - The commands above, and a C test of listxattr() sizes and buffer
> lengths: a file with only FinderInfo gives 0 without the patch and
> 25 with it; a file without extended attributes gives 0 on both.
> - generic/062: 10/10 passed on both kernels.
> - Full fstests (805 generic tests, 608 not run on both kernels): 186
> passed and 11 failed without the patch, 187 and 10 with it. The
> only
> difference is generic/795, which fails at random on both kernels
> with fsck "Invalid volume file count" (1 of 11 runs without the
> patch, 2 of 11 with it). generic/089 and a small test that only
> creates files and unlinks them while open hit the same error on
> both
> kernels. This looks like a separate race: hfsplus_file_release()
> updates file_count without vh_mutex.
>
> With this patch, getfattr above prints "osx.com.apple.FinderInf". The
> last character is lost by a separate bug in copy_name(), which
> Maurycy
> Pawlowski-Wieronski's patch fixes:
> https://lore.kernel.org/all/20260828-hfsplus-copy_name-fix-v1-1-75ed9f0f378c@maurycy.com/
>
> fs/hfsplus/xattr.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/fs/hfsplus/xattr.c b/fs/hfsplus/xattr.c
> index 71364e093fa7..45571d6f3abd 100644
> --- a/fs/hfsplus/xattr.c
> +++ b/fs/hfsplus/xattr.c
> @@ -837,13 +837,9 @@ ssize_t hfsplus_listxattr(struct dentry *dentry,
> char *buffer, size_t size)
>
> err = hfsplus_find_attr(inode->i_sb, inode->i_ino, NULL,
> &fd);
> if (err) {
> - if (err == -ENOENT || err == -ENODATA) {
> - res = 0;
> - goto end_listxattr;
> - } else {
> + if (err != -ENOENT && err != -ENODATA)
> res = err;
> - goto end_listxattr;
> - }
> + goto end_listxattr;
> }
>
> for (;;) {
>
> base-commit: a804c5742bff224d4cb4d25dd383554d598be32b
Looks good.
Reviewed-by: Viacheslav Dubeyko <slava@dubeyko.com>
Thanks,
Slava.
prev parent reply other threads:[~2026-10-22 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 9:40 Hengyu Liang
2026-10-22 18:49 ` Viacheslav Dubeyko [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=a5830eb2ef9f0dfd43a9cd1255caa3f9f77541f1.camel@dubeyko.com \
--to=slava@dubeyko.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hengyul@cs.unc.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®