On Tue, Jul 14, 2026 at 09:32:27AM +0530, Aneesh Kumar K.V wrote: > If we want to warn about such failures, we should add the warning > consistently across the code. We may also want to handle decrypt > failures by encrypting the page again to avoid leaking it. > > I will work on that as a tree-wide change in a separate patch.
IMHO the WARN should be inside set_memory_encrypted(), and maybe it should be a BUG_ON... "free" functions shouldn't fail, and returning the memory back to normal is a "free" operation. Jason
