man2: update glibc wrapper status and clean up FIXMEs
PATCH 1/2 man2: update glibc wrapper status and clean up FIXMEs
Update seccomp(2) to reflect that glibc 2.33 added a wrapper. Update sched_setattr(2) to remove obsolete FIXME markers, as the lack of a glibc wrapper is already correctly noted in the text.
Signed-off-by Simon Essien <[email protected]>
--- man/man2/sched_setattr.2 | 5 +---- man/man2/seccomp.2 | 4 ++-- 2 files changed, 3 insertions(+), 6 deletions(-)
man/man2/sched_setattr.2 +1 -4
@@ -460,7 +460,6 @@ does not include all CPUs in the system Linux. .SH HISTORY Linux 3.14. -.\" FIXME . Add glibc version .SH NOTES glibc does not provide wrappers for these system calls; call them using
@@ -482,9 +481,7 @@ provides a superset of the functionality of and (partially) .BR getpriority (2). .SH BUGS -In Linux versions up to -.\" FIXME . patch sent to Peter Zijlstra -3.15, +In Linux versions up to 3.15, .BR sched_setattr () failed with the error .B EFAULT
man/man2/seccomp.2 +2 -2
@@ -25,7 +25,7 @@ Standard C library .fi .P .IR Note : -glibc provides no wrapper for +Before glibc 2.33, glibc provided no wrapper for .BR seccomp (), necessitating the use of .BR syscall (2).
@@ -863,7 +863,7 @@ be determined. Linux. .SH HISTORY Linux 3.17. -.\" FIXME . Add glibc version +Glibc 2.33. .SH NOTES Rather than hand-coding seccomp filters as shown in the example below, you may prefer to employ the
Signature · 1 line
2.51.0
PATCH 2/2 path_resolution.7: document read-only mounts, ACLs, and immutable files
Address several FIXMEs by adding brief mentions of:
- EROFS errors on read-only filesystems.
- Access restrictions from filesystem ACLs.
- Access restrictions from immutable file attributes.
Signed-off-by Simon Essien <[email protected]>
--- man/man7/path_resolution.7 | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-)
man/man7/path_resolution.7 +15 -3
@@ -225,7 +225,12 @@ Similarly, Linux uses the fsgid ("filesystem group ID") instead of the effective group ID. See .BR setfsgid (2). -.\" FIXME . say something about filesystem mounted read-only ? +.P +Even if a process has the necessary permissions to access or +modify a file, an attempt to modify any part of the filesystem +will fail with the error +.B EROFS +if the filesystem is currently mounted read-only. .SS Bypassing permission checks: superuser and capabilities On a traditional UNIX system, the superuser .RI ( root ,
@@ -256,8 +261,15 @@ The .B CAP_DAC_READ_SEARCH capability grants read and search permission on directories, and read permission on ordinary files. -.\" FIXME . say something about immutable files -.\" FIXME . say something about ACLs +.P +Beyond the standard permissions, access may also be restricted by +filesystem-specific ACLs (Access Control Lists) or by +immutable file attributes. +See +.BR acl (5) +and +.BR chattr (1) +for more details. .SH SEE ALSO .BR readlink (2), .BR capabilities (7),
Signature · 1 line
2.51.0