linux-kernel - Re: can't mmap PCI legacy

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] [day] [month] [year] [list]

Date:	Tue, 13 Jan 2009 08:41:09 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Daniel Drake <dsd@...too.org>
Cc:	linux kernel <linux-kernel@...r.kernel.org>,
	linuxppc-dev@...abs.org, dliana@...ntiernet.net
Subject: Re: can't mmap PCI legacy_mem on Powerbook G4

On Mon, 2009-01-12 at 11:29 +0000, Daniel Drake wrote:
> Hi,
> 
> Dave reports a 2.6.28 regression here:
> https://bugs.gentoo.org/show_bug.cgi?id=253149
> 
> X (server v1.5.3) no longer starts, it aborts with a mmap() error.
> 
> 
> This is because X tries to use sysfs pci legacy_mem to map the VGA frame 
> buffer if it is available, and this became available in 2.6.28 for ppc, 
> but the mmap() fails with -ENXIO.

Argh... Can the X folks stop being full of sh*t ? I'll have to have a
look there, fortunately, I'm occasionally one of them :-)

I made the files available on all powerpc, however, not all platforms
support legacy mem access. The PowerBook doesn't, which is why it
returns the error. It would be more complicated to make the file's
existence conditional instead, but I'll loo kat it.

In the meantime, please file an X bug. It shouldn't fallback to /proc or
whatever junk it did with /dev/mem, it should understand that as "the
kernel supports the legacy interfaces, and tells you this machine has no
access to legacy mem" and thus disable all attempts at whacking VGA text
mode.

Ben.

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