From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] fscrypt: support decrypting data from large folios
Date: Fri, 3 Feb 2023 13:57:51 -0800 [thread overview]
Message-ID: <Y92DX1eB9HT58YJ1@sol.localdomain> (raw)
In-Reply-To: <20230127224202.355629-1-ebiggers@kernel.org>
On Fri, Jan 27, 2023 at 02:42:02PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Try to make the filesystem-level decryption functions in fs/crypto/
> aware of large folios. This includes making fscrypt_decrypt_bio()
> support the case where the bio contains large folios, and making
> fscrypt_decrypt_pagecache_blocks() take a folio instead of a page.
>
> There's no way to actually test this with large folios yet, but I've
> tested that this doesn't cause any regressions.
>
> Note that this patch just handles *decryption*, not encryption which
> will be a little more difficult.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> Documentation/filesystems/fscrypt.rst | 4 ++--
> fs/buffer.c | 4 ++--
> fs/crypto/bio.c | 10 ++++------
> fs/crypto/crypto.c | 28 ++++++++++++++-------------
> fs/ext4/inode.c | 6 ++++--
> include/linux/fscrypt.h | 9 ++++-----
> 6 files changed, 31 insertions(+), 30 deletions(-)
Applied to https://git.kernel.org/pub/scm/fs/fsverity/linux.git/log/?h=for-next
(I used the fsverity tree instead of the fscrypt tree, so that I could resolve
the conflict with "fs/buffer.c: support fsverity in block_read_full_folio()" in
the fsverity tree.)
- Eric
prev parent reply other threads:[~2023-02-03 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 22:42 [PATCH] fscrypt: support decrypting data from large folios Eric Biggers
2023-01-27 23:33 ` Matthew Wilcox
2023-01-27 23:41 ` Eric Biggers
2023-02-03 21:57 ` Eric Biggers [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=Y92DX1eB9HT58YJ1@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).