d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

- Don't suggest opening file for writing in preparation for fexecve(2).

Browse Source 
- execve(2)/fexecve(2) won't return ETXTBSY if file is open for reading.

Approved by:	re (kib)
This commit is contained in:
pjd 2009-07-05 20:20:09 +00:00
parent 9f7eae50be
commit fb7ddfc9fe
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
lib/libc/sys/execve.2
View File

@ -220,13 +220,11 @@ Since execute permission is checked by
.Fn fexecve ,
the file descriptor
.Fa fd
need not have been
opened with the
need not have been opened with the
.Dv O_EXEC
flag.
However, if the file to be executed denies read and write
permission for the process preparing to do the exec, the only way to
provide the
However, if the file to be executed denies read permission for the process
preparing to do the exec, the only way to provide the
.Fa fd
to
.Fn fexecve
@ -234,6 +232,7 @@ is to use the
.Dv O_EXEC
flag when opening
.Fa fd .
Note that the file to be executed can not be open for writing.
.Sh RETURN VALUES
As the
.Fn execve
@ -277,7 +276,7 @@ The new process file has the appropriate access
permission, but has an invalid magic number in its header.
.It Bq Er ETXTBSY
The new process file is a pure procedure (shared text)
file that is currently open for writing or reading by some process.
file that is currently open for writing by some process.
.It Bq Er ENOMEM
The new process requires more virtual memory than
is allowed by the imposed maximum