lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 9 Jul 2020 14:59:23 -0700 From: Eric Biggers <ebiggers@...nel.org> To: Satya Tangirala <satyat@...gle.com> Cc: linux-fscrypt@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net, linux-ext4@...r.kernel.org Subject: Re: [PATCH 3/5] iomap: support direct I/O with fscrypt using blk-crypto On Thu, Jul 09, 2020 at 07:47:49PM +0000, Satya Tangirala wrote: > From: Eric Biggers <ebiggers@...gle.com> > > Wire up iomap direct I/O with the fscrypt additions for direct I/O, > and set bio crypt contexts on bios when appropriate. It might be useful to mention why the calls to fscrypt_limit_dio_pages() are needed. (It's because the iomap code works directly with logical ranges, so it doesn't have a chance to do fscrypt_mergeable_bio() on every page.) > > Signed-off-by: Eric Biggers <ebiggers@...gle.com> > Signed-off-by: Satya Tangirala <satyat@...gle.com> > --- > fs/iomap/direct-io.c | 8 ++++++++ > 1 file changed, 8 insertions(+) You probably should add linux-xfs@...r.kernel.org to Cc, as per './scripts/get_maintainer.pl fs/iomap/'. - Eric
Powered by blists - more mailing lists