aboutsummaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@woody.linux-foundation.org>2007-05-04 20:44:23 -0700
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-05-04 20:44:23 -0700
commit6cbf0c704d7c3bb215ae7e0381b1ff2ad5931f35 (patch)
treef2979bdafe0e0644fb82975a30993d03da7f8fd4 /crypto
parent4d4700707c0d4be0efc968989fb1cd01c60c0a35 (diff)
iomap: make the default iomap functions fail softer
We used to BUG_ON() for a badly mapped IO port, which is certainly correct, but actually made it harder to debug the case where the ATA drivers had incorrectly mapped a nonconnected ATA port. So make badly mapped ports trigger a WARN_ON(), and throw the IO away instead (and return all ones for reads). For things like broken driver initialization - which is the most likely cause anyway - that should mean that the machine comes up and is usable (at least that was the case for the ATA breakage that triggered this patch). It tends to be a whole lot easier to do a "dmesg" on a working machine than to try to capture logs off a dead one. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions