From: Alejandro Colomar <alx@kernel.org>
To: Rik van Riel <riel@surriel.com>
Cc: linux-man@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
kernel-team@meta.com, Eric Biederman <ebiederm@xmission.com>
Subject: Re: [PATCH] execve.2: execve also returns E2BIG if a string is too long
Date: Wed, 11 Oct 2023 12:41:13 +0200 [thread overview]
Message-ID: <ZSZ7yXwYAg-xPC7P@debian> (raw)
In-Reply-To: <20231010234153.021826b1@imladris.surriel.com>
[-- Attachment #1: Type: text/plain, Size: 1935 bytes --]
Hi Rik,
On Tue, Oct 10, 2023 at 11:41:53PM -0400, Rik van Riel wrote:
> Document that if a command line or environment string is too long (> MAX_ARG_STRLEN), execve will also return E2BIG.
That's already implied by the current text:
E2BIG The total number of bytes in the environment (envp) and argument
list (argv) is too large.
That means that
size_t bytes;
bytes = 0;
for (char *e = envp; e != NULL; e++)
bytes += strlen(e) + 1; // I have doubts about the +1
for (char *a = argv; a != NULL; a++)
bytes += strlen(a) + 1; // Same doubts
if (bytes > MAX_ARG_STRLEN) // Maybe >= ?
return -E2BIG;
>
> Signed-off-by: Rik van Riel <riel@surriel.com>
> ---
> man2/execve.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/execve.2 b/man2/execve.2
> index 0d9582492ad1..c1a359d01872 100644
> --- a/man2/execve.2
> +++ b/man2/execve.2
> @@ -449,7 +449,7 @@ The total number of bytes in the environment
> .RI ( envp )
> and argument list
> .RI ( argv )
> -is too large.
> +is too large, or an argument or environment string is too long.
Please use semantic newlines:
$ MANWIDTH=72 man man-pages | sed -n '/Use semantic newlines/,/^$/p'
Use semantic newlines
In the source of a manual page, new sentences should be started
on new lines, long sentences should be split into lines at
clause breaks (commas, semicolons, colons, and so on), and long
clauses should be split at phrase boundaries. This convention,
sometimes known as "semantic newlines", makes it easier to see
the effect of patches, which often operate at the level of in‐
dividual sentences, clauses, or phrases.
Thanks,
Alex
> .TP
> .B EACCES
> Search permission is denied on a component of the path prefix of
> --
> 2.41.0
>
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-11 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 3:41 [PATCH] execve.2: execve also returns E2BIG if a string is too long Rik van Riel
2023-10-11 10:41 ` Alejandro Colomar [this message]
2023-10-11 13:21 ` Rik van Riel
2023-10-11 13:44 ` Matthew House
2023-10-11 14:44 ` Alejandro Colomar
2023-10-11 14:47 ` Alejandro Colomar
2023-10-11 15:11 ` Matthew House
2023-10-11 15:50 ` Alejandro Colomar
2023-10-11 14:42 ` Alejandro Colomar
2023-10-11 13:52 ` Matthew House
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZSZ7yXwYAg-xPC7P@debian \
--to=alx@kernel.org \
--cc=ebiederm@xmission.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=riel@surriel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox