Re: [RFC 08/19] exec: add API specification for execve

2025-06-17 Thread Sasha Levin
On Tue, Jun 17, 2025 at 09:13:44AM +0200, Florian Weimer wrote: * Sasha Levin: On Mon, Jun 16, 2025 at 11:39:31PM +0200, Florian Weimer wrote: * Sasha Levin: + KAPI_RETURN("long", "Does not return on success; returns -1 on error") + .type = KAPI_TYPE_INT, +

Re: [RFC 08/19] exec: add API specification for execve

2025-06-17 Thread Florian Weimer
* Sasha Levin: > On Mon, Jun 16, 2025 at 11:39:31PM +0200, Florian Weimer wrote: >>* Sasha Levin: >> >>> + KAPI_RETURN("long", "Does not return on success; returns -1 on error") >>> + .type = KAPI_TYPE_INT, >>> + .check_type = KAPI_RETURN_ERROR_CHECK, >>> + KAPI_RETURN_END

Re: [RFC 08/19] exec: add API specification for execve

2025-06-16 Thread Sasha Levin
On Mon, Jun 16, 2025 at 11:39:31PM +0200, Florian Weimer wrote: * Sasha Levin: + KAPI_RETURN("long", "Does not return on success; returns -1 on error") + .type = KAPI_TYPE_INT, + .check_type = KAPI_RETURN_ERROR_CHECK, + KAPI_RETURN_END Is the -1 part co

Re: [RFC 08/19] exec: add API specification for execve

2025-06-16 Thread Florian Weimer
* Sasha Levin: > + KAPI_RETURN("long", "Does not return on success; returns -1 on error") > + .type = KAPI_TYPE_INT, > + .check_type = KAPI_RETURN_ERROR_CHECK, > + KAPI_RETURN_END Is the -1 part correct? Many later errors during execve are not recoverable and resu

[RFC 08/19] exec: add API specification for execve

2025-06-14 Thread Sasha Levin
Add comprehensive kernel API specification for the execve() system call. Signed-off-by: Sasha Levin --- fs/exec.c | 218 ++ 1 file changed, 218 insertions(+) diff --git a/fs/exec.c b/fs/exec.c index 1f5fdd2e096e3..3d006105ab23d 100644 --- a/fs