Page MenuHomeFreeBSD

system(3): Fix null case
ClosedPublic

Authored by des on Feb 24 2026, 1:44 PM.
Tags
None
Referenced Files
F172669811: D55484.id172585.diff
Sun, Sep 20, 2:25 AM
F172668184: D55484.id172712.diff
Sun, Sep 20, 2:09 AM
F172667818: D55484.diff
Sun, Sep 20, 2:06 AM
Unknown Object (File)
Sat, Sep 12, 8:54 PM
Unknown Object (File)
Sat, Sep 12, 2:52 PM
Unknown Object (File)
Thu, Sep 10, 7:18 AM
Unknown Object (File)
Thu, Sep 10, 1:24 AM
Unknown Object (File)
Wed, Sep 9, 4:15 AM
Subscribers

Details

Summary

Our manual page states that if given a null pointer, system() returns
non-zero if the shell is available and zero if it is not. This is
consistent with the C standard's description of system(), but it is not
what we actually do. What we actually do is always return non-zero, as
required by POSIX.

As the POSIX rationale explains, implementing the logic required by the
C standard does not violate POSIX, since a conforming system always has
a shell, therefore the logic will always return non-zero.

Since our libc is commonly used in non-conforming situations such as
chroots or thin jails, we should implement the full logic required by
the C standard.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable