From: patchwork-bot+f2fs@kernel.org
To: Daniel Rosenberg <drosen@google.com>
Cc: jaegeuk@kernel.org, kernel-team@android.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: Restrict max filesize for 16K f2fs
Date: Thu, 14 Dec 2023 20:50:32 +0000 [thread overview]
Message-ID: <170258703202.30587.16093975604922475515.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231205023801.3669458-1-drosen@google.com>
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
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
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
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: Restrict max filesize for 16K f2fs
Date: Thu, 14 Dec 2023 20:50:32 +0000 [thread overview]
Message-ID: <170258703202.30587.16093975604922475515.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231205023801.3669458-1-drosen@google.com>
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
next prev parent reply other threads:[~2023-12-14 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 2:38 [f2fs-dev] [PATCH v3] f2fs: Restrict max filesize for 16K f2fs Daniel Rosenberg via Linux-f2fs-devel
2023-12-05 2:38 ` Daniel Rosenberg
2023-12-14 20:50 ` patchwork-bot+f2fs [this message]
2023-12-14 20:50 ` [f2fs-dev] " patchwork-bot+f2fs
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=170258703202.30587.16093975604922475515.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=drosen@google.com \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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.