linux-kernel - Re: man-pages-2.57 is released

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Jun 2007 16:06:36 +0200
From:	Bodo Eggert <7eggert@....de>
To:	Michael Kerrisk <mtk-manpages@....net>,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: man-pages-2.57 is released

Michael Kerrisk <mtk-manpages@....net> wrote:

> ./man2/ioperm.2
>      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.

You now have the full 64Kb port bitmap (8 KB).


BTW1: linux/arch/i386/kernel/ioport.c still states having 8K of bitmaps to
be excessive (and implicitely and now wrongly as not being done). Since
there should only be few processes requiring iopl, the 8K should not be
excessive. We need a native speaker to change this text, at least not me
right now.

CC Linus, because he admitted fiddeling with this file. (No MAINTAINER found)


BTW2: My (possibly outdated) iopl manpage states that you'll need to be root
change the iopl, but you only need CAP_SYS_RAWIO in order to increase the
iopl.
-- 
Have you ever noticed that the Klingons are all speaking unix?
"Grep ls awk chmod."   "Mknod ksh tar imap."
"Wall fsck yacc!"     (that last is obviously a curse of some sort)
        -- Gandalf  Parker
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/