From: Chao Yu <chao@kernel.org>
To: Keshav Verma <iganschel@gmail.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: fix listxattr handling of corrupted xattr entries
Date: Mon, 22 Jun 2026 09:23:41 +0800 [thread overview]
Message-ID: <f2827427-4b83-4334-9201-fd8f62246875@kernel.org> (raw)
In-Reply-To: <20260618200105.3551-1-iganschel@gmail.com>
On 6/19/26 04:01, Keshav Verma wrote:
> Validate the xattr entry before reading its fields in f2fs_listxattr().
> Return -EFSCORRUPTED when the entry is outside the valid xattr storage
> area instead of returning a successful partial result.
>
Fixes line and Cc: stable@kernel.org
> Signed-off-by: Keshav Verma <iganschel@gmail.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
> ---
> fs/f2fs/xattr.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/fs/f2fs/xattr.c b/fs/f2fs/xattr.c
> index 610d5810074d..18f495db20d2 100644
> --- a/fs/f2fs/xattr.c
> +++ b/fs/f2fs/xattr.c
> @@ -581,8 +581,6 @@ ssize_t f2fs_listxattr(struct dentry *dentry, char *buffer, size_t buffer_size)
> size_t prefix_len;
> size_t size;
>
> - prefix = f2fs_xattr_prefix(entry->e_name_index, dentry);
> -
> if ((void *)(entry) + sizeof(__u32) > last_base_addr ||
> (void *)XATTR_NEXT_ENTRY(entry) > last_base_addr) {
> f2fs_err(F2FS_I_SB(inode), "list inode (%llu) has corrupted xattr",
> @@ -590,9 +588,12 @@ ssize_t f2fs_listxattr(struct dentry *dentry, char *buffer, size_t buffer_size)
> set_sbi_flag(F2FS_I_SB(inode), SBI_NEED_FSCK);
> f2fs_handle_error(F2FS_I_SB(inode),
> ERROR_CORRUPTED_XATTR);
> - break;
> + error = -EFSCORRUPTED;
> + goto cleanup;
> }
>
> + prefix = f2fs_xattr_prefix(entry->e_name_index, dentry);
> +
> if (!prefix)
> continue;
>
next prev parent reply other threads:[~2026-06-22 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 20:01 Keshav Verma
2026-06-22 1:23 ` Chao Yu [this message]
2026-06-22 15:14 ` [PATCH v2] " Keshav Verma
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=f2827427-4b83-4334-9201-fd8f62246875@kernel.org \
--to=chao@kernel.org \
--cc=iganschel@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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
Powered by JetHome