From: Jaegeuk Kim <jaegeuk@kernel.org>
To: LiaoYuanhong-vivo <liaoyuanhong@vivo.com>
Cc: ebiggers@kernel.org, chao@kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, tytso@mit.edu
Subject: Re: [PATCH v2 0/3] f2fs: support encrypted inline data
Date: Mon, 15 Jun 2026 03:04:35 +0000 [thread overview]
Message-ID: <ai9rw8tjybY8Aiqu@google.com> (raw)
In-Reply-To: <20260611125006.508734-1-liaoyuanhong@vivo.com>
On 06/11, LiaoYuanhong-vivo wrote:
> Hi,
>
> Gentle ping on this series.
>
> v2 tries to address the previous concerns by avoiding per-file software
> tfm growth, preparing the software transform lazily, and explicitly
> disabling unsupported key combinations.
>
> The main remaining limitation is hardware-wrapped keys. If this makes
> the feature unlikely to be accepted, please let me know. Otherwise, I
> would appreciate any review comments on the current direction.
Yeah, that'd be a big win, if we have the hardware-wrapped key support. By
any chance, can you add it in the patch set?
>
> If maintainers have any feasible direction in mind, I would also
> appreciate hearing it.
>
> Thanks,
> Liao Yuanhong
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: LiaoYuanhong-vivo <liaoyuanhong@vivo.com>
Cc: corbet@lwn.net, tytso@mit.edu, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, ebiggers@kernel.org,
linux-fscrypt@vger.kernel.org, skhan@linuxfoundation.org
Subject: Re: [f2fs-dev] [PATCH v2 0/3] f2fs: support encrypted inline data
Date: Mon, 15 Jun 2026 03:04:35 +0000 [thread overview]
Message-ID: <ai9rw8tjybY8Aiqu@google.com> (raw)
In-Reply-To: <20260611125006.508734-1-liaoyuanhong@vivo.com>
On 06/11, LiaoYuanhong-vivo wrote:
> Hi,
>
> Gentle ping on this series.
>
> v2 tries to address the previous concerns by avoiding per-file software
> tfm growth, preparing the software transform lazily, and explicitly
> disabling unsupported key combinations.
>
> The main remaining limitation is hardware-wrapped keys. If this makes
> the feature unlikely to be accepted, please let me know. Otherwise, I
> would appreciate any review comments on the current direction.
Yeah, that'd be a big win, if we have the hardware-wrapped key support. By
any chance, can you add it in the patch set?
>
> If maintainers have any feasible direction in mind, I would also
> appreciate hearing it.
>
> Thanks,
> Liao Yuanhong
_______________________________________________
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:[~2026-06-15 3:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 13:40 [PATCH v2 0/3] f2fs: support encrypted inline data LiaoYuanhong-vivo
2026-06-02 13:40 ` [f2fs-dev] " LiaoYuanhong-vivo via Linux-f2fs-devel
2026-06-02 13:41 ` [PATCH v2 1/3] fscrypt: prepare software keys for filesystem-managed data units LiaoYuanhong-vivo
2026-06-02 13:41 ` [PATCH v2 2/3] f2fs: support encrypted inline data LiaoYuanhong-vivo
2026-06-02 13:41 ` [f2fs-dev] " LiaoYuanhong-vivo via Linux-f2fs-devel
2026-06-02 13:41 ` [PATCH v2 3/3] Documentation: f2fs: document " LiaoYuanhong-vivo
2026-06-02 13:41 ` [f2fs-dev] " LiaoYuanhong-vivo via Linux-f2fs-devel
2026-06-11 12:50 ` [PATCH v2 0/3] f2fs: support " LiaoYuanhong-vivo
2026-06-11 12:50 ` [f2fs-dev] " LiaoYuanhong-vivo via Linux-f2fs-devel
2026-06-15 3:04 ` Jaegeuk Kim [this message]
2026-06-15 3:04 ` Jaegeuk Kim via Linux-f2fs-devel
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=ai9rw8tjybY8Aiqu@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=liaoyuanhong@vivo.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tytso@mit.edu \
/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.