From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Christoph Hellwig <hch@lst.de>,
"Darrick J . Wong" <djwong@kernel.org>,
Dave Chinner <david@fromorbit.com>,
Satya Tangirala <satyat@google.com>
Subject: Re: [PATCH v11 4/5] f2fs: support direct I/O with fscrypt using blk-crypto
Date: Fri, 28 Jan 2022 16:27:43 -0800 [thread overview]
Message-ID: <YfSJ/xstxw8mFw80@google.com> (raw)
In-Reply-To: <20220128233940.79464-5-ebiggers@kernel.org>
On 01/28, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Encrypted files traditionally haven't supported DIO, due to the need to
> encrypt/decrypt the data. However, when the encryption is implemented
> using inline encryption (blk-crypto) instead of the traditional
> filesystem-layer encryption, it is straightforward to support DIO.
>
> Therefore, make f2fs support DIO on files that are using inline
> encryption. Since f2fs uses iomap for DIO, and fscrypt support was
> already added to iomap DIO, this just requires two small changes:
>
> - Let DIO proceed when supported, by checking fscrypt_dio_supported()
> instead of assuming that encrypted files never support DIO.
>
> - In f2fs_iomap_begin(), use fscrypt_limit_io_blocks() to limit the
> length of the mapping in the rare case where a DUN discontiguity
> occurs in the middle of an extent. The iomap DIO implementation
> requires this, since it assumes that it can submit a bio covering (up
> to) the whole mapping, without checking fscrypt constraints itself.
>
> Co-developed-by: Satya Tangirala <satyat@google.com>
> Signed-off-by: Satya Tangirala <satyat@google.com>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Acked-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/data.c | 7 +++++++
> fs/f2fs/f2fs.h | 6 +++++-
> 2 files changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 8c417864c66ae..020d47f97969c 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -4044,6 +4044,13 @@ static int f2fs_iomap_begin(struct inode *inode, loff_t offset, loff_t length,
>
> iomap->offset = blks_to_bytes(inode, map.m_lblk);
>
> + /*
> + * When inline encryption is enabled, sometimes I/O to an encrypted file
> + * has to be broken up to guarantee DUN contiguity. Handle this by
> + * limiting the length of the mapping returned.
> + */
> + map.m_len = fscrypt_limit_io_blocks(inode, map.m_lblk, map.m_len);
> +
> if (map.m_flags & (F2FS_MAP_MAPPED | F2FS_MAP_UNWRITTEN)) {
> iomap->length = blks_to_bytes(inode, map.m_len);
> if (map.m_flags & F2FS_MAP_MAPPED) {
> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
> index eb22fa91c2b26..db46f3cf0885d 100644
> --- a/fs/f2fs/f2fs.h
> +++ b/fs/f2fs/f2fs.h
> @@ -4371,7 +4371,11 @@ static inline bool f2fs_force_buffered_io(struct inode *inode,
> struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
> int rw = iov_iter_rw(iter);
>
> - if (f2fs_post_read_required(inode))
> + if (!fscrypt_dio_supported(iocb, iter))
> + return true;
> + if (fsverity_active(inode))
> + return true;
> + if (f2fs_compressed_file(inode))
> return true;
>
> /* disallow direct IO if any of devices has unaligned blksize */
> --
> 2.35.0
next prev parent reply other threads:[~2022-01-29 0:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 23:39 [PATCH v11 0/5] add support for direct I/O with fscrypt using blk-crypto Eric Biggers
2022-01-28 23:39 ` [PATCH v11 1/5] fscrypt: add functions for direct I/O support Eric Biggers
2022-02-01 8:06 ` Christoph Hellwig
2022-01-28 23:39 ` [PATCH v11 2/5] iomap: support direct I/O with fscrypt using blk-crypto Eric Biggers
2022-01-28 23:39 ` [PATCH v11 3/5] ext4: " Eric Biggers
2022-01-28 23:39 ` [PATCH v11 4/5] f2fs: " Eric Biggers
2022-01-29 0:27 ` Jaegeuk Kim [this message]
2022-01-28 23:39 ` [PATCH v11 5/5] fscrypt: update documentation for direct I/O support Eric Biggers
2022-02-01 8:07 ` Christoph Hellwig
2022-02-11 6:17 ` [PATCH v11 0/5] add support for direct I/O with fscrypt using blk-crypto Eric Biggers
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=YfSJ/xstxw8mFw80@google.com \
--to=jaegeuk@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=satyat@google.com \
--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 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 NNTP newsgroup(s).