linux-kernel - Re: [PATCH] Fix PCI resource mmaping on sparc64

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]

Message-Id: <20081031.120238.156698095.davem@davemloft.net>
Date:	Fri, 31 Oct 2008 12:02:38 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dmitrmax@...il.com
Cc:	linux-kernel@...r.kernel.org, sparclinux@...r.kernel.org
Subject: Re: [PATCH] Fix PCI resource mmaping on sparc64

From: "Max Dmitrichenko" <dmitrmax@...il.com>
Date: Fri, 31 Oct 2008 16:09:48 +0300

Please post sparc patches to the sparclinux mailing list,
CC:'d

> There is a problem discovered in recent versions of ATI Mach64 driver
> in X.org on sparc64 architecture. In short, the driver fails to mmap
> MMIO aperture (PCI resource #2).
> 
> I've found that kernel's __pci_mmap_make_offset() returns EINVAL. It
> checks whether user attempts to mmap more than the resource length,
> which is 0x1000 bytes in our case. But PAGE_SIZE on SPARC64 is 0x2000
> and this is what actually is being mmaped. So __pci_mmap_make_offset()
> failed for this PCI resource.
> 
> Signed-off-by: Max Dmitrichenko <dmitrmax@...il.com>
> 
> Code seems to be rather old. At least it was the same in 2.6.24. I
> have no explanation why this bug exposed only now. May be before X.org
> used to use some other method to mmap PCI resource into userspace (now
> it uses libpciaccess).
> 
> The patch is against 2.6.26. Greg, please consider to include it into
> the stable trees.

No, the sparc maintainer (that's me) will submit this patch to -stable
if it is correct and appropriate.
--
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/