From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Satya Tangirala <satyat@google.com>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH v4 5/7] f2fs: support direct I/O with fscrypt using blk-crypto
Date: Tue, 21 Jul 2020 13:11:43 -0700 [thread overview]
Message-ID: <20200721201143.GB43066@google.com> (raw)
In-Reply-To: <20200720233739.824943-6-satyat@google.com>
On 07/20, Satya Tangirala wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Wire up f2fs with fscrypt direct I/O support. direct I/O with fscrypt is
> only supported through blk-crypto (i.e. CONFIG_BLK_INLINE_ENCRYPTION must
> have been enabled, the 'inlinecrypt' mount option must have been specified,
> and either hardware inline encryption support must be present or
> CONFIG_BLK_INLINE_ENCYRPTION_FALLBACK must have been enabled). Further,
> direct I/O on encrypted files is only supported when I/O is aligned
> to the filesystem block size (which is *not* necessarily the same as the
> block device's block size).
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> Co-developed-by: Satya Tangirala <satyat@google.com>
> Signed-off-by: Satya Tangirala <satyat@google.com>
Acked-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/f2fs.h | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
> index b35a50f4953c..978130b5a195 100644
> --- a/fs/f2fs/f2fs.h
> +++ b/fs/f2fs/f2fs.h
> @@ -4082,7 +4082,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;
> if (f2fs_is_multi_device(sbi))
> return true;
> --
> 2.28.0.rc0.105.gf9edc3c819-goog
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Satya Tangirala <satyat@google.com>
Cc: Eric Biggers <ebiggers@google.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v4 5/7] f2fs: support direct I/O with fscrypt using blk-crypto
Date: Tue, 21 Jul 2020 13:11:43 -0700 [thread overview]
Message-ID: <20200721201143.GB43066@google.com> (raw)
In-Reply-To: <20200720233739.824943-6-satyat@google.com>
On 07/20, Satya Tangirala wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Wire up f2fs with fscrypt direct I/O support. direct I/O with fscrypt is
> only supported through blk-crypto (i.e. CONFIG_BLK_INLINE_ENCRYPTION must
> have been enabled, the 'inlinecrypt' mount option must have been specified,
> and either hardware inline encryption support must be present or
> CONFIG_BLK_INLINE_ENCYRPTION_FALLBACK must have been enabled). Further,
> direct I/O on encrypted files is only supported when I/O is aligned
> to the filesystem block size (which is *not* necessarily the same as the
> block device's block size).
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> Co-developed-by: Satya Tangirala <satyat@google.com>
> Signed-off-by: Satya Tangirala <satyat@google.com>
Acked-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/f2fs.h | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
> index b35a50f4953c..978130b5a195 100644
> --- a/fs/f2fs/f2fs.h
> +++ b/fs/f2fs/f2fs.h
> @@ -4082,7 +4082,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;
> if (f2fs_is_multi_device(sbi))
> return true;
> --
> 2.28.0.rc0.105.gf9edc3c819-goog
_______________________________________________
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:[~2020-07-21 20:11 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 23:37 [PATCH v4 0/7] add support for direct I/O with fscrypt using blk-crypto Satya Tangirala
2020-07-20 23:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-07-20 23:37 ` [PATCH v4 1/7] fscrypt: Add functions for direct I/O support Satya Tangirala
2020-07-20 23:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-07-22 17:04 ` Jaegeuk Kim
2020-07-22 17:04 ` [f2fs-dev] " Jaegeuk Kim
2020-07-20 23:37 ` [PATCH v4 2/7] direct-io: add support for fscrypt using blk-crypto Satya Tangirala
2020-07-20 23:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-07-22 17:05 ` Jaegeuk Kim
2020-07-22 17:05 ` [f2fs-dev] " Jaegeuk Kim
2020-07-20 23:37 ` [PATCH v4 3/7] iomap: support direct I/O with " Satya Tangirala
2020-07-20 23:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-07-22 17:06 ` Jaegeuk Kim
2020-07-22 17:06 ` [f2fs-dev] " Jaegeuk Kim
2020-07-22 21:16 ` Dave Chinner
2020-07-22 21:16 ` [f2fs-dev] " Dave Chinner
2020-07-22 22:34 ` Eric Biggers
2020-07-22 22:34 ` [f2fs-dev] " Eric Biggers
2020-07-22 22:44 ` Matthew Wilcox
2020-07-22 22:44 ` [f2fs-dev] " Matthew Wilcox
2020-07-22 23:12 ` Eric Biggers
2020-07-22 23:12 ` [f2fs-dev] " Eric Biggers
2020-07-22 23:26 ` Eric Biggers
2020-07-22 23:26 ` [f2fs-dev] " Eric Biggers
2020-07-22 23:32 ` Darrick J. Wong
2020-07-22 23:32 ` [f2fs-dev] " Darrick J. Wong
2020-07-22 23:43 ` Eric Biggers
2020-07-22 23:43 ` [f2fs-dev] " Eric Biggers
2020-07-23 22:07 ` Dave Chinner
2020-07-23 22:07 ` [f2fs-dev] " Dave Chinner
2020-07-23 23:03 ` Eric Biggers
2020-07-23 23:03 ` [f2fs-dev] " Eric Biggers
2020-07-24 1:39 ` Dave Chinner
2020-07-24 1:39 ` [f2fs-dev] " Dave Chinner
2020-07-24 3:46 ` Eric Biggers
2020-07-24 3:46 ` [f2fs-dev] " Eric Biggers
2020-07-24 5:31 ` Dave Chinner
2020-07-24 5:31 ` [f2fs-dev] " Dave Chinner
2020-07-24 17:41 ` Eric Biggers
2020-07-24 17:41 ` [f2fs-dev] " Eric Biggers
2020-07-25 23:47 ` Dave Chinner
2020-07-25 23:47 ` [f2fs-dev] " Dave Chinner
2020-07-25 23:59 ` Dave Chinner
2020-07-25 23:59 ` [f2fs-dev] " Dave Chinner
2020-07-26 2:42 ` Eric Biggers
2020-07-26 2:42 ` [f2fs-dev] " Eric Biggers
2020-07-27 17:16 ` Eric Biggers
2020-07-27 17:16 ` [f2fs-dev] " Eric Biggers
2020-07-20 23:37 ` [PATCH v4 4/7] ext4: " Satya Tangirala
2020-07-20 23:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-07-22 17:07 ` Jaegeuk Kim
2020-07-22 17:07 ` [f2fs-dev] " Jaegeuk Kim
2020-07-20 23:37 ` [PATCH v4 5/7] f2fs: " Satya Tangirala
2020-07-20 23:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-07-21 20:11 ` Jaegeuk Kim [this message]
2020-07-21 20:11 ` Jaegeuk Kim
2020-07-20 23:37 ` [PATCH v4 6/7] fscrypt: document inline encryption support Satya Tangirala
2020-07-20 23:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-07-22 17:01 ` Jaegeuk Kim
2020-07-22 17:01 ` [f2fs-dev] " Jaegeuk Kim
2020-07-20 23:37 ` [PATCH v4 7/7] fscrypt: update documentation for direct I/O support Satya Tangirala
2020-07-20 23:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-07-21 0:47 ` Eric Biggers
2020-07-21 0:47 ` [f2fs-dev] " Eric Biggers
2020-07-22 16:57 ` Jaegeuk Kim
2020-07-22 16:57 ` [f2fs-dev] " Jaegeuk Kim
2020-07-21 0:56 ` [PATCH v4 0/7] add support for direct I/O with fscrypt using blk-crypto Eric Biggers
2020-07-21 0:56 ` [f2fs-dev] " 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=20200721201143.GB43066@google.com \
--to=jaegeuk@kernel.org \
--cc=ebiggers@google.com \
--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 \
/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.