From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/4 v2] fsck|dump.f2fs: add -M to get file map
Date: Thu, 8 Jul 2021 14:30:51 +0800 [thread overview]
Message-ID: <bb003f7c-eca0-92e2-613e-2c5d859b29ba@kernel.org> (raw)
In-Reply-To: <YNNbk/AI2T6fkhLC@google.com>
On 2021/6/24 0:04, Jaegeuk Kim wrote:> static void dump_data_blk(struct f2fs_sb_info *sbi, __u64 offset, u32 blkaddr)
> {
> char buf[F2FS_BLKSIZE];
>
> + if (c.show_file_map) {
> + if (c.show_file_map_max_offset < offset) {
> + ASSERT(blkaddr == NULL_ADDR);
> + return;
> + }
> + if (blkaddr == NULL_ADDR || blkaddr == NEW_ADDR ||
> + blkaddr == COMPRESS_ADDR) {
is_valid_data_blkaddr()
> @@ -1685,6 +1721,12 @@ int fsck_chk_dentry_blk(struct f2fs_sb_info *sbi, int casefolded, u32 blk_addr,
> ASSERT(ret >= 0);
>
> fsck->dentry_depth++;
> + new_dentry = calloc(sizeof(struct f2fs_dentry), 1);
ASSERT(new_dentry != NULL);
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
next prev parent reply other threads:[~2021-07-08 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 2:39 [f2fs-dev] [PATCH 1/4] mkfs.f2fs: remove android features for RO Jaegeuk Kim
2021-06-21 2:39 ` [f2fs-dev] [PATCH 2/4] fsck|dump.f2fs: add -M to get file map Jaegeuk Kim
2021-06-23 14:28 ` Chao Yu
2021-06-23 16:04 ` [f2fs-dev] [PATCH 2/4 v2] " Jaegeuk Kim
2021-07-08 6:30 ` Chao Yu [this message]
2021-06-21 2:39 ` [f2fs-dev] [PATCH 3/4] f2fs-tools: fix wrong file offset Jaegeuk Kim
2021-06-23 14:47 ` Chao Yu
2021-06-23 16:03 ` Jaegeuk Kim
2021-06-21 2:39 ` [f2fs-dev] [PATCH 4/4] f2fs-tools: add extent cache for each file Jaegeuk Kim
2021-06-23 13:51 ` [f2fs-dev] [PATCH 1/4] mkfs.f2fs: remove android features for RO Chao Yu
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=bb003f7c-eca0-92e2-613e-2c5d859b29ba@kernel.org \
--to=chao@kernel.org \
--cc=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).