From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [PATCH 2/2] fsck.f2fs: wrong report on xattr boundary
Date: Sat, 28 Oct 2023 16:48:13 -0700 [thread overview]
Message-ID: <20231028234813.496851-2-jaegeuk@kernel.org> (raw)
In-Reply-To: <20231028234813.496851-1-jaegeuk@kernel.org>
This avoids false alarm on xfstests/generic/425.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fsck/xattr.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fsck/xattr.c b/fsck/xattr.c
index e291ef4740ba..3163639b9d41 100644
--- a/fsck/xattr.c
+++ b/fsck/xattr.c
@@ -44,6 +44,9 @@ void *read_all_xattrs(struct f2fs_sb_info *sbi, struct f2fs_node *inode,
get_node_info(sbi, xnid, &ni);
ret = dev_read_block(txattr_addr + inline_size, ni.blk_addr);
ASSERT(ret >= 0);
+ memset(txattr_addr + inline_size + F2FS_BLKSIZE -
+ sizeof(struct node_footer), 0,
+ sizeof(struct node_footer));
}
header = XATTR_HDR(txattr_addr);
--
2.42.0.820.g83a721a137-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2023-10-28 23:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 23:48 [f2fs-dev] [PATCH 1/2] f2fs-tools: use F2FS_BLKSIZE by default Jaegeuk Kim
2023-10-28 23:48 ` Jaegeuk Kim [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=20231028234813.496851-2-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).