On Tue, Apr 28, 2026, Ackerley Tng wrote: > This is RFC v5 of guest_memfd in-place conversion support.
... > TODOs > > + Perhaps further clarify PRESERVE flag: [8] > + Resolve issue where guest_memfd_conversions_test, which uses the > kselftest framework, doesn't perform teardown on assertion > failure. Please see proposal at [9] > + Test with TDX selftests. We're in the process of rebasing TDX selftests > on this series and will post updates when that's tested. Why exactly is this still RFC? The TODOs here don't strike me as things that would make this RFC. Blockers for merge, yes/maybe/probably, but at a glance, it feels like we've moved beyond RFC for the code itself.
