On Mon, Jun 09, 2025 at 07:47:38AM +0900, Damien Le Moal wrote: > To be honest, I have never tested the block layer inline crypto feature using > zoned devices. All the use cases I have with crypto are using dm-crypt. > A quick look tells me that the issue is with that particular feature, especially > the fallback path, as it is using work items to asynchronously handle write data > encryption. Nothing asynchronous in the fallback write path, just weird open coded bio splitting like the one I just got rid of with the bounce buffering.. > One additional thing: why do you need f2fs with your reproducer ? Problems > should happen also doing writes directly to the block device, no ? Because fscrypt is the only user of the block crypto code, and f2fs is the only user of that that works on zoned devices.
