From: Robin Murphy <robin.murphy@arm.com>
To: Alexander Duyck <alexander.h.duyck@linux.intel.com>,
iommu@lists.linux-foundation.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux@roeck-us.net, gregkh@linuxfoundation.org
Subject: Re: [PATCH] dma-direct: Fix return value of dma_direct_supported
Date: Thu, 4 Oct 2018 12:25:47 +0100 [thread overview]
Message-ID: <5329f992-d3aa-c16c-1218-c26d758889b8@arm.com> (raw)
In-Reply-To: <20181003234746.3586.42014.stgit@localhost.localdomain>
On 04/10/18 00:48, Alexander Duyck wrote:
> 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.
Bah, seems I got hung up on the min_mask code above it and totally
overlooked that the condition itself got flipped. It probably also can't
help that it's an int return type, but treated as a bool by callers
rather than "0 for success" as int tends to imply in isolation.
Anyway, paying a bit more attention this time, I think this looks like
the right fix - cheers Alex.
Robin.
> 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>
> ---
> kernel/dma/direct.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
> index 5a0806b5351b..65872f6c2e93 100644
> --- a/kernel/dma/direct.c
> +++ b/kernel/dma/direct.c
> @@ -301,9 +301,7 @@ int dma_direct_supported(struct device *dev, u64 mask)
>
> min_mask = min_t(u64, min_mask, (max_pfn - 1) << PAGE_SHIFT);
>
> - if (mask >= phys_to_dma(dev, min_mask))
> - return 0;
> - return 1;
> + return mask >= phys_to_dma(dev, min_mask);
> }
>
> int dma_direct_mapping_error(struct device *dev, dma_addr_t dma_addr)
>
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
>
next prev parent reply other threads:[~2018-10-04 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 23:48 [PATCH] dma-direct: Fix return value of dma_direct_supported Alexander Duyck
2018-10-04 11:25 ` Robin Murphy [this message]
2018-10-04 15:13 ` Alexander Duyck
2018-10-05 7:17 ` Christoph Hellwig
2018-12-13 19:45 ` Lendacky, Thomas
2018-12-13 19:58 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5329f992-d3aa-c16c-1218-c26d758889b8@arm.com \
--to=robin.murphy@arm.com \
--cc=alexander.h.duyck@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).