diff options
author | FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> | 2008-10-23 18:42:03 +0900 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2008-10-23 21:54:38 +0200 |
commit | a2b89b596c5a0b288adac84b17bdda6bde8d144e (patch) | |
tree | cb33305ff4f30ceaba1c5cbd0eef84d68edca942 /fs/gfs2/recovery.h | |
parent | ff3c536291ce96ef6f45704cd37eaed71127dd42 (diff) | |
download | op-kernel-dev-a2b89b596c5a0b288adac84b17bdda6bde8d144e.zip op-kernel-dev-a2b89b596c5a0b288adac84b17bdda6bde8d144e.tar.gz |
swiotlb: remove panic for alloc_coherent failure
swiotlb_alloc_coherent calls panic() when allocated swiotlb pages is
not fit for a device's dma mask. However, alloc_coherent failure is
not a disaster at all. AFAIK, none of other x86 and IA64 IOMMU
implementations don't crash in case of alloc_coherent failure.
There are some drivers that don't check alloc_coherent failure but not
many (about ten and I've already started to fix some of
them). alloc_coherent returns NULL in case of failure so it's likely
that these guilty drivers crash immediately. So swiotlb doesn't need
to call panic() just for them.
Reported-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Tested-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'fs/gfs2/recovery.h')
0 files changed, 0 insertions, 0 deletions