diff options
author | David S. Miller <davem@davemloft.net> | 2009-12-09 01:39:09 -0800 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2009-12-09 01:39:09 -0800 |
commit | 4230fa3b89ea1c413766bd411a8315a3d05aa6c7 (patch) | |
tree | 9d916501338c43239137fdf639fef0e2b14b21ef /crypto/hash.c | |
parent | a252e749f1ae17e43ccc5824f7b1b5854417c98b (diff) |
sparc64: Fix overly strict range type matching for PCI devices.
When we are trying to see if a range property entry applies
to a given address, we are overly strict about the type.
We should only allow I/O ranges for I/O addresses, and only allow
CONFIG space ranges for CONFIG space address.
However for MEM ranges, they come in 32-bit and 64-bit flavors.
And a lack of an exact match is OK if the range is 32-bit and
the address is 64-bit. We can assign a 64-bit address properly
into a 32-bit parent range just fine.
So allow it.
Reported-by: Patrick Finnegan <pat@computer-refuge.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto/hash.c')
0 files changed, 0 insertions, 0 deletions