Re: [PATCH v2 0/2] luo: migrate serialized_data to type-safe KHO pointers

[tarunsahu]

Pratyush Yadav <pratyush@xxxxxxxxxx> writes:

> On Fri, Jun 19 2026, tarunsahu@xxxxxxxxxx wrote:
>
>> +Mike, +Pasha
>>
>> This is currently rebased on top of mailine, also can be applied to
>> liveupdate/fixes with no conflict. I would like to know which release
>> cycle we are targeting for this, so That I can rebase it accordingly?
>>
>> As for liveupdate/next, it needs some conlfict resolution.
>
> Base it on liveupdate/next after the merge window. Since nothing is
> actively broken (as far as I can tell), I don't think we should take it
> via fixes. We should do it via the 7.3 merge window.

This is gonna be used in guest_memfd preservation as well. Next version
(V3) Should be based on top of it. And if we delay this (as it is gonna
be with liveupdate/next) it will delay the review cycle of guest_memfd
as well.

~Tarun
>
>>
>> Tarun Sahu <tarunsahu@xxxxxxxxxx> writes:
>>
>>> Covvert raw serialized_data to KHO serializeable pointer (KHOSER_PTR).
>>> This series also takes care of resolving the bug with memfd of using
>>> phys_to_virt before checking the args->serialized_data value.
> [...]
>
> -- 
> Regards,
> Pratyush Yadav