linux-kernel - Re: [PATCH 1/2] char/mem: Add /dev/io (v2)

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20120208001724.7e5c7be4@pyramind.ukuu.org.uk>
Date:	Wed, 8 Feb 2012 00:17:24 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Adam Jackson <ajax@...hat.com>
Cc:	linux-kernel@...r.kernel.org, arnd@...db.de,
	gregkh@...uxfoundation.org
Subject: Re: [PATCH 1/2] char/mem: Add /dev/io (v2)

On Tue,  7 Feb 2012 18:39:45 -0500
Adam Jackson <ajax@...hat.com> wrote:

> This is like /dev/port except not broken.  /dev/port will translate all
> read/write into inb/outb streams, which is wrong since hardware can and
> does care about cycle size.  /dev/io will only allow 1, 2, or 4 byte
> access, and will translate that into the appropriate bus cycle size.

>From a security perspective /dev/[k][mem is a dumb bit of ancient Unix
history we'd dearly like to kill off. /dev/port is a similar early PC
unixism that wants to go the same way. /dev/io just adds another horror
to the pile.

Please do the decent thing, stop using /dev/mem and /dev/port for
anything. If you need to access an I/O device make it properly visible
via the kernel only for the ports and in a manner that is safe.

Alan
--
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/