src/lib/libc/sys/execve.2, branch release/9.3.0FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=release%2F9.3.02010-09-21T16:24:51ZFix exec_imgact_shell()'s handling of two error cases: (1) Previously, if2010-09-21T16:24:51ZAlan Coxalc@FreeBSD.org2010-09-21T16:24:51Zurn:sha1:8f7f5a7f26ba1c1f1af672f1975d2b5fb57a051b
the first line of a script exceeded MAXSHELLCMDLEN characters, then
exec_imgact_shell() silently truncated the line and passed on the truncated
interpreter name or argument. Now, exec_imgact_shell() will fail and return
ENOEXEC, which is the commonly used errno among Unix variants for this type
of error. (2) Previously, exec_imgact_shell()'s check on the length of the
interpreter's name was ineffective. In other words, exec_imgact_shell()
could not possibly fail and return ENAMETOOLONG. The reason being that the
length of the interpreter name had to exceed MAXSHELLCMDLEN characters in
order that ENAMETOOLONG be returned. But, the search for the end of the
interpreter name stops after at most MAXSHELLCMDLEN - 2 characters are
scanned. (In the end, this particular error is eventually discovered
outside of exec_imgact_shell() and ENAMETOOLONG is returned. So, the real
effect of this second change is that the error is detected earlier, in
exec_imgact_shell().)
Update the definition of MAXINTERP to the actual limit on the size of
the interpreter name that has been in effect since r142453 (from
2005).
In collaboration with: kib
mdoc: move CAVEATS, BUGS and SECURITY CONSIDERATIONS sections to the2010-05-13T12:07:55ZUlrich Spörleinuqs@FreeBSD.org2010-05-13T12:07:55Zurn:sha1:0afc94c17a8772df34294778904e816258542498
bottom of the manpages and order them consistently.
GNU groff doesn't care about the ordering, and doesn't even mention
CAVEATS and SECURITY CONSIDERATIONS as common sections and where to put
them.
Found by: mdocml lint run
Reviewed by: ru
Update xrefs from 4.3BSD to modern signal functions in various man pages.2010-05-06T22:49:54ZJilles Tjoelkerjilles@FreeBSD.org2010-05-06T22:49:54Zurn:sha1:c84cab5626f45a39acf9c322e9b45f4459d0300b
sigvec(2) references have been updated to sigaction(2), sigsetmask(2) and
sigblock(2) to sigprocmask(2), sigpause(2) to sigsuspend(2).
Some legacy man pages still refer to them, that is OK.
- Don't suggest opening file for writing in preparation for fexecve(2).2009-07-05T20:20:09ZPawel Jakub Dawidekpjd@FreeBSD.org2009-07-05T20:20:09Zurn:sha1:69a789b9855506bcfcde109c260c7aefb8574a68
- execve(2)/fexecve(2) won't return ETXTBSY if file is open for reading.
Approved by: re (kib)
When calculating arguments to the interpreter for the shebang script2008-08-26T10:53:32ZKonstantin Belousovkib@FreeBSD.org2008-08-26T10:53:32Zurn:sha1:eaad10997300d844f4754815a89e3890ab7b7539
executed by fexecve(2), imgp->args->fname is NULL. Moreover, there is
no way to recover the path to the script being executed.
Do what some other U*ixes do unconditionally, namely supply /dev/fd/n
as the script path when called from fexecve(). Document requirement of
having fdescfs mounted as caveat.
Man pages for the openat(2), fexecve(2) and related syscalls.2008-04-16T13:03:12ZKonstantin Belousovkib@FreeBSD.org2008-04-16T13:03:12Zurn:sha1:a141af6930ff64262ef4d0fd13f4edf8e266d5fe
Reviewed by: ru
Per Regents of the University of Calfornia letter, remove advertising2007-01-09T00:28:16ZWarner Loshimp@FreeBSD.org2007-01-09T00:28:16Zurn:sha1:c879ae3536e6d92b8d96c8965c5b05fcb9541520
clause.
# If I've done so improperly on a file, please let me know.
Sort SEE ALSO references (in dictionary order, ignoring case).2004-07-04T20:55:50ZRuslan Ermilovru@FreeBSD.org2004-07-04T20:55:50Zurn:sha1:1c85060a1336f3d13c474b01bf8ce4d997ca3793Eliminate double whitespace.2004-07-03T22:30:10ZRuslan Ermilovru@FreeBSD.org2004-07-03T22:30:10Zurn:sha1:30950a21e11892bddfb8f6b190ee2b693803cddfMechanically kill hard sentence breaks.2004-07-02T23:52:20ZRuslan Ermilovru@FreeBSD.org2004-07-02T23:52:20Zurn:sha1:1a0a934547909744a6a2fa4cfd5b795ec6394f05