From: Chao Yu <chao@kernel.org>
To: Daniel Rosenberg <drosen@google.com>,
linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, kernel-team@android.com
Subject: Re: [f2fs-dev] [PATCH] dump.f2fs: Fix dumping inlined files
Date: Tue, 18 Jun 2024 11:01:22 +0800 [thread overview]
Message-ID: <1f1657f2-aec9-4ee9-9b9b-4bb6cb45d01c@kernel.org> (raw)
In-Reply-To: <20240618004136.1336922-1-drosen@google.com>
On 2024/6/18 8:41, Daniel Rosenberg wrote:
> The code for dumping files was ignoring i_extra_isize, leading to
> invalid data for some inlined files after dumping. This swaps inode
> dumping to use the common inline_data_addr function.
>
> Signed-off-by: Daniel Rosenberg <drosen@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
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:[~2024-06-18 3:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 0:41 [f2fs-dev] [PATCH] dump.f2fs: Fix dumping inlined files Daniel Rosenberg via Linux-f2fs-devel
2024-06-18 3:01 ` Chao Yu [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=1f1657f2-aec9-4ee9-9b9b-4bb6cb45d01c@kernel.org \
--to=chao@kernel.org \
--cc=drosen@google.com \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@android.com \
--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).