On Fri, Dec 01, 2023 at 05:11:23PM -0500, Josef Bacik wrote: > We keep track of this information in the ordered extent for writes, but > we need it for reads as well. Add fscrypt_extent_info and orig_start to > the dio_data so we can populate this on reads. This will be used later > when we attach the fscrypt context to the bios. > > Signed-off-by: Josef Bacik <josef@xxxxxxxxxxxxxx> Does this mean that btrfs will support direct I/O on encrypted files from the beginning? Are you enforcing FS block alignment, as is required for encrypted direct I/O? - Eric
