dma-direct: fix return value of dma_direct_supported
authorAlexander Duyck <alexander.h.duyck@linux.intel.com>
Wed, 3 Oct 2018 23:48:07 +0000 (16:48 -0700)
committerChristoph Hellwig <hch@lst.de>
Fri, 5 Oct 2018 07:15:15 +0000 (09:15 +0200)
commit1fc8e6423edb4bba365b0780c2fcddfb921b24b2
treea628cadf739b7d945e5c2375365b1cfa6f8906cc
parent6db37ad7c27bda2f62d1ef6ad0496e359c562c1a
dma-direct: fix return value of dma_direct_supported

It appears that in commit 9d7a224b463e ("dma-direct: always allow dma mask
<= physiscal memory size") the logic of the test was changed from a "<" to
a ">=" however I don't see any reason for that change. I am assuming that
there was some additional change planned, specifically I suspect the logic
was intended to be reversed and possibly used for a return. Since that is
the case I have gone ahead and done that.

This addresses issues I had on my system that prevented me from booting
with the above mentioned commit applied on an x86_64 system w/ Intel IOMMU.

Fixes: 9d7a224b463e ("dma-direct: always allow dma mask <= physiscal memory size")
Signed-off-by: Alexander Duyck <alexander.h.duyck@linux.intel.com>
Acked-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
kernel/dma/direct.c