On Fri, Mar 17, 2023 at 03:52:40PM +0100, Roberto Sassu wrote: > +The `UMD Manager` is the frontend interface to any user or > +kernel-originated request. It invokes the `UMD Loader` to start the > +`UMD Handler`, and communicates with the latter to satisfy the request. > + > +The `UMD Loader` is merely responsible to extract the `user binary` from > +the kernel module, copy it to a tmpfs filesystem, fork the current process, > +start the `UMD Handler`, and create a pipe for the communication between > +the `UMD Manager` and the `UMD Handler`. > + > +The `UMD Handler` reads requests from the `UMD Manager`, processes them > +internally, and sends the response to it. I think you can write out the full forms (UMD manager, UMD loader, and UMD handler) once and for subsequent mentions of these, UMD can be omitted, since the manager/loader/handler will obviously refers to the UMD one. Otherwise LGTM, thanks! Reviewed-by: Bagas Sanjaya <bagasdotme@xxxxxxxxx> -- An old man doll... just what I always wanted! - Clara
Attachment:
signature.asc
Description: PGP signature
