Re: [PATCH 2/2] linux: posix_spawn: return EINVAL on argc < 1

[Joseph Myers <joseph@codesourcery.com>]

On Fri, 28 Jan 2022, Cristian Rodríguez wrote:

> On Fri, Jan 28, 2022 at 8:26 PM Joseph Myers <joseph@codesourcery.com> wrote:
> >
> > On Fri, 28 Jan 2022, Adhemerval Zanella via Libc-alpha wrote:
> >
> > > We can add a note on deprecated and removed features, but I am not sure
> > > if would make any difference now that kernels will changes the semantic
> > > anyway and it will cause compatibility issues anyway.
> >
> > I haven't seen any discussions of this on linux-api, so the kernel
> > discussion elsewhere might not be taking any compatibility issues properly
> > into account.
> 
> but making things in libc calling execve potentially  with argc == 0
> error out or behave like having argv = {"", NULL} shouldn't break
> anything right ?

Errors for argc == 0 (with argv != NULL) are contrary to POSIX, which 
allows that case other than for Strictly Conforming POSIX Applications, 
that being the meaning of "should" here.  (It's possible that in fact many 
applications that would break also use argv == NULL, which isn't valid in 
POSIX, rather than argv pointing to an array containing a single NULL 
pointer, which is valid.)

-- 
Joseph S. Myers
joseph@codesourcery.com