summaryrefslogtreecommitdiff
path: root/crypto/chainiv.c
diff options
context:
space:
mode:
authorDavid Miller <davem@davemloft.net>2009-02-12 02:15:27 -0800
committerDave Airlie <airlied@redhat.com>2009-03-13 14:23:59 +1000
commit5a7aad9a559a5488cbef7aa3d4d96fc28220b8ae (patch)
tree4a35fea85696e6cd41c81c71f34c2f7cf086aae3 /crypto/chainiv.c
parent8e1004580e0c862cb6bbe2ff8e496f846c54052f (diff)
downloadlinux-3.10-5a7aad9a559a5488cbef7aa3d4d96fc28220b8ae.tar.gz
linux-3.10-5a7aad9a559a5488cbef7aa3d4d96fc28220b8ae.tar.bz2
linux-3.10-5a7aad9a559a5488cbef7aa3d4d96fc28220b8ae.zip
drm: ati_pcigart: Do not access I/O MEM space using pointer derefs.
The PCI GART table initialization code treats the GART table mapping unconditionally as a kernel virtual address. But it could be in the framebuffer, for example, and thus we're dealing with a PCI MEM space ioremap() cookie. Treating that as a virtual address is illegal and will crash some system types (such as sparc64 where the ioremap() return value is actually a physical I/O address). So access the area correctly, using gart_info->gart_table_location as our guide. Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Dave Airlie <airlied@linux.ie>
Diffstat (limited to 'crypto/chainiv.c')
0 files changed, 0 insertions, 0 deletions