This documentation really confused me and needs to be updated. H. Peter Anvin, the maintainer for this part of the kernel, emailed me to clarify that the 0x3ff limit has been gone since Linux 2.6.8.
Signed-off-by: Alex Henrie <alexh@xxxxxxxxxx>
---
man2/ioperm.2 | 14 +++++---------
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/man2/ioperm.2 b/man2/ioperm.2
index 3470a8d..11304aa 100644
--- a/man2/ioperm.2
+++ b/man2/ioperm.2
@@ -51,15 +51,6 @@ sets the port access permission bits for the calling process for
If \fIturn_on\fP is nonzero, the calling process must be privileged
.RB ( CAP_SYS_RAWIO ).
-.\" FIXME is the following ("Only the first 0x3ff I/O ports can be
-.\" specified in this manner") still true? Looking at changes in
-.\" include/asm-i386/processor.h between 2.4 and 2.6 suggests
-.\" that the limit is different in 2.6.
-Only the first 0x3ff I/O ports can be specified in this manner.
-For more ports, the
-.BR iopl (2)
-system call must be used.
-
Permissions are not inherited by the child created by
.BR fork (2).
Permissions are preserved across
@@ -105,6 +96,11 @@ Glibc2 has a prototype both in
and in
.IR <sys/perm.h> .
Avoid the latter, it is available on i386 only.
+
+Before Linux 2.6.8, only the first 0x3ff I/O ports could be specified
+in this manner. For more ports on older kernels, the
+.BR iopl (2)
+system call must be used.
.SH "SEE ALSO"
.BR iopl (2),
.BR capabilities (7)
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
