close_range.2: Correct the explanation of the EMFILE error

close_range() CLOSE_RANGE_USHARE triggers a call to dup_fd()
which in turn calls alloc_fdtable(), which checks that
sysctl_nr_open has not been exceeded.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2021-03-21 16:32:20 +01:00
parent 368ace8467
commit e3e22b2b2b
1 changed files with 10 additions and 5 deletions

View File

@ -79,11 +79,16 @@ The following can occur with
(when constructing the new descriptor table):
.TP
.B EMFILE
The per-process limit on the number of open file descriptors has been reached
(see the description of
.B RLIMIT_NOFILE
in
.BR getrlimit (2)).
The number of open file descriptors exceeds the limit specified in
.IR /proc/sys/fs/nr_open
(see
.BR proc (5)).
This error can occur in situations where that limit was lowered before
a call to
.BR close_range ()
where the
.B CLOSE_RANGE_UNSHARE
flag is specified.
.TP
.B ENOMEM
Insufficient kernel memory was available.