Comment 1 for bug 1958926

I've seen the issues with backporting the upstream fix into 2.2 and it does not look like something that is recommended. I'm working with the customer to see if the workaround of using `--disable-luks2-reencryption` to mitigate their security concerns is a good solution.