Re: [PATCH v4 2/2] luo: Update serialized data to use KHOSER_PTR
| Newsgroups | org.infradead.lists.kexec,org.kernel.vger.linux-kernel,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
Mike Rapoport <[email protected]> writes: > On Tue, Jun 23, 2026 at 09:56:40AM +0000, [email protected] wrote: >> Mike Rapoport <[email protected]> writes: >> >> > On Mon, 22 Jun 2026 22:57:36 +0000, Tarun Sahu <[email protected]> wrote: >> >> Convert 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. >> > >> > For easier backporting the memfd fix should be a standalone commit that >> > comes first in the series. >> > >> > Other than that >> >> It will break compilation for individual patch. For example, memfd_luo >> changes are hard coded dependent on the args->serialized_data >> conversion to KHOSER_PTR? >> >> Maybe I did not understand, Could you please explain what you mean? > > Sorry I wasn't clear. > If people think it's important to have the memfd_luo fix in 7.1, the fix > should be the first patch in the series and shouldn't use KHOSER pointers. I dont think, this is critical issue. But it will be a good practice. I sent v5 with these changes. Thanks for the review! ~Tarun > >> > >> > Acked-by: Mike Rapoport (Microsoft) <[email protected]> >> > >> > -- >> > Sincerely yours, >> > Mike. > > -- > Sincerely yours, > Mike.