On 5/25/25 10:24 PM, Christoph Hellwig wrote:
On Fri, May 23, 2025 at 09:30:36AM -0700, Bart Van Assche wrote:
It is the dm-default-key driver, a driver about which everyone
(including the authors of that driver) agree that it should disappear.
Unfortunately the functionality provided by that driver has not yet been
integrated in the upstream kernel (encrypt filesystem metadata).
How that driver (dm-default-key) works is very similar to how dm-crypt
works. I think that the most important difference is that dm-crypt
requests encryption for all bios while dm-default-key only sets an
encryption key for a subset of the bios it processes.
Umm, Bart I really expected better from you. You're ducking around
providing a reproducer for over a week and waste multiple peoples
time to tell us the only reproducer is your out of tree thingy
reject upstream before? That's not really how Linux developement
works.
I'm still working on a reproducer for the blktests framework. To my own
frustration I have not yet found a small reproducer that is easy to run
by others. I'm convinced that it should be possible to create a
reproducer that is based on dm-crypt since dm-crypt and the dm-default-
key driver behave identically with regard to bio splitting.
Bart.
