Received-SPF: pass (google.com: domain of linux-kernel+bounces-90-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: Restrict max filesize for 16K f2fs
From: patchwork-bot+f2fs@kernel.org
Message-Id: 
 <170258703202.30587.16093975604922475515.git-patchwork-notify@kernel.org>
Date: Thu, 14 Dec 2023 20:50:32 +0000
References: <20231205023801.3669458-1-drosen@google.com>
In-Reply-To: <20231205023801.3669458-1-drosen@google.com>
To: Daniel Rosenberg <drosen@google.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
 kernel-team@android.com, linux-kernel@vger.kernel.org

Hello:

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

On Mon,  4 Dec 2023 18:38:01 -0800 you wrote:
> Blocks are tracked by u32, so the max permitted filesize is
> (U32_MAX + 1) * BLOCK_SIZE. Additionally, in order to support crypto
> data unit sizes of 4K with a 16K block with IV_INO_LBLK_{32,64}, we must
> further restrict max filesize to (U32_MAX + 1) * 4096. This does not
> affect 4K blocksize f2fs as the natural limit for files are well below
> that.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v3] f2fs: Restrict max filesize for 16K f2fs
    https://git.kernel.org/jaegeuk/f2fs/c/a6a010f5def5

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