On Fri, Nov 14 2025, Pasha Tatashin wrote: > On Fri, Nov 14, 2025 at 12:18 PM Pratyush Yadav <[email protected]> wrote: >> >> On Fri, Nov 14 2025, Pasha Tatashin wrote: >> >> > Previously, KHO required a dedicated kho_abort() function to clean up >> > state before kho_finalize() could be called again. This was necessary >> > to handle complex unwind paths when using notifiers. >> > >> > With the shift to direct memory preservation, the explicit abort step >> > is no longer strictly necessary. >> > >> > Remove kho_abort() and refactor kho_finalize() to handle re-entry. >> > If kho_finalize() is called while KHO is already finalized, it will >> > now automatically clean up the previous memory map and state before >> > generating a new one. This allows the KHO state to be updated/refreshed >> > simply by triggering finalize again. >> > >> > Update debugfs to return -EINVAL if userspace attempts to write 0 to >> > the finalize attribute, as explicit abort is no longer supported. >> >> Documentation/core-api/kho/concepts.rst touches on the concept of >> finalization. I suppose that should be updated as well. > > I looked at it, and it is vague, we are soon to remove finalize with > stateless kho from Jason Miu, so in that series that section can be > removed or replaced.
Okay, fair enough. [...] -- Regards, Pratyush Yadav
