Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: Fix system crash due to lack of free
 space in LFS
From:   patchwork-bot+f2fs@kernel.org
Message-Id: <167993282009.32120.676262168059778051.git-patchwork-notify@kernel.org>
Date:   Mon, 27 Mar 2023 16:00:20 +0000
References: <20230321001251epcms2p4c1fd48495643dbfca2cf82a433490bb8@epcms2p4>
In-Reply-To: <20230321001251epcms2p4c1fd48495643dbfca2cf82a433490bb8@epcms2p4>
To:     Yonggil Song <yonggil.song@samsung.com>
Cc:     jaegeuk@kernel.org, chao@kernel.org,
        linux-f2fs-devel@lists.sourceforge.net,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Tue, 21 Mar 2023 09:12:51 +0900 you wrote:
> When f2fs tries to checkpoint during foreground gc in LFS mode, system
> crash occurs due to lack of free space if the amount of dirty node and
> dentry pages generated by data migration exceeds free space.
> The reproduction sequence is as follows.
> 
>  - 20GiB capacity block device (null_blk)
>  - format and mount with LFS mode
>  - create a file and write 20,000MiB
>  - 4k random write on full range of the file
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v2] f2fs: Fix system crash due to lack of free space in LFS
    https://git.kernel.org/jaegeuk/f2fs/c/86003b7460ed

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html