All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: liujinbao1 <jinbaoliu365@gmail.com>
Cc: Sheng Yong <shengyong1@xiaomi.com>,
	liujinbao1 <liujinbao1@xiaomi.com>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] inject.f2fs: fix injecting nat/sit journal in compact summary
Date: Tue, 14 Jul 2026 02:45:07 +0000	[thread overview]
Message-ID: <alWis0rOEibilsuc@google.com> (raw)
In-Reply-To: <20260530123038.2101877-1-jinbaoliu365@gmail.com>

Could you please rebase on top of f2fs-tools?

Thanks,

On 05/30, liujinbao1 wrote:
> From: liujinbao1 <liujinbao1@xiaomi.com>
> 
> When CP has CP_COMPACT_SUM_FLAG set, the nat/sit journal is stored in
> compact summary blocks at start_sum_block() rather than in the regular
> summary area. However, rewrite_nat_in_journal() and
> rewrite_sit_in_journal() only handled CP_UMOUNT_FLAG and the running
> state, missing the compact summary case.This caused the fault injection
> to fail.
> 
> Fix this by adding the CP_COMPACT_SUM_FLAG check before the existing
> CP_UMOUNT_FLAG check in both functions, writing the journal to the
> correct compact summary block location.
> 
> Test steps:
> 1. NAT journal injection (nid=4, quota file):
>   inject.f2fs --nat 0 --mb block_addr --nid 4 --val 12345 /dev/block/by-name/userdata
>   Before: blkaddr unchanged (308225)
>   After:  blkaddr = 12345
> 
> 2. SIT journal injection (segno=61075, CURSEG_COLD_DATA):
>   inject.f2fs --sit 0 --blk 0x1e1da00 --mb vblocks --val 123 /dev/block/by-name/userdata
>   Before: vblocks unchanged (0)
>   After:  vblocks = 123
> 
> Signed-off-by: Sheng Yong <shengyong1@xiaomi.com>
> Signed-off-by: liujinbao1 <liujinbao1@xiaomi.com>
> ---
>  fsck/inject.c | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/fsck/inject.c b/fsck/inject.c
> index b00e356..60a2d20 100644
> --- a/fsck/inject.c
> +++ b/fsck/inject.c
> @@ -675,6 +675,14 @@ static void rewrite_nat_in_journal(struct f2fs_sb_info *sbi, u32 nid,
>  		}
>  	}
>  
> +	if (is_set_ckpt_flags(cp, CP_COMPACT_SUM_FLAG)) {
> +		blkaddr = start_sum_block(sbi);
> +		ret = dev_write(&journal->n_nats, blkaddr << F2FS_BLKSIZE_BITS,
> +				SUM_JOURNAL_SIZE, WRITE_LIFE_NONE);
> +		ASSERT(ret >= 0);
> +		return;
> +	}
> +
>  	if (is_set_ckpt_flags(cp, CP_UMOUNT_FLAG))
>  		blkaddr = sum_blk_addr(sbi, NR_CURSEG_TYPE, CURSEG_HOT_DATA);
>  	else
> @@ -806,6 +814,14 @@ static void rewrite_sit_in_journal(struct f2fs_sb_info *sbi, unsigned int segno,
>  		}
>  	}
>  
> +	if (is_set_ckpt_flags(cp, CP_COMPACT_SUM_FLAG)) {
> +		blkaddr = start_sum_block(sbi);
> +		ret = dev_write(&journal->n_sits, (blkaddr << F2FS_BLKSIZE_BITS) + SUM_JOURNAL_SIZE,
> +				SUM_JOURNAL_SIZE, WRITE_LIFE_NONE);
> +		ASSERT(ret >= 0);
> +		return;
> +	}
> +
>  	if (is_set_ckpt_flags(cp, CP_UMOUNT_FLAG))
>  		blkaddr = sum_blk_addr(sbi, NR_CURSEG_TYPE, CURSEG_COLD_DATA);
>  	else
> -- 
> 2.43.0
> 
> 
> 
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      parent reply	other threads:[~2026-07-14  2:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30 12:30 [f2fs-dev] [PATCH] inject.f2fs: fix injecting nat/sit journal in compact summary liujinbao1
2026-07-02 14:16 ` liujinbao1
2026-07-08  2:34 ` Chao Yu via Linux-f2fs-devel
2026-07-14  2:45 ` Jaegeuk Kim via Linux-f2fs-devel [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=alWis0rOEibilsuc@google.com \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=jaegeuk@kernel.org \
    --cc=jinbaoliu365@gmail.com \
    --cc=liujinbao1@xiaomi.com \
    --cc=shengyong1@xiaomi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.