From: Gary R Hook <gary.hook@amd.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu: Limit the IOVA page range to the specified addresses
Date: Fri, 27 Oct 2017 10:20:43 -0500 [thread overview]
Message-ID: <df434365-6972-f87c-c77b-f0008aa2b1c8@amd.com> (raw)
In-Reply-To: <20171026103201.6ac9f21c@t450s.home>
On 10/26/2017 03:32 AM, Alex Williamson wrote:
> On Tue, 17 Oct 2017 16:22:01 -0500
> Gary R Hook <gary.hook@amd.com> wrote:
>
>> From: amd <amd@sosxen2.amd.com>
>>
>> The extent of pages specified when applying a reserved region should
>> include up to the last page of the range, but not the page following
>> the range.
>>
>> Signed-off-by: Gary R Hook <gary.hook@amd.com>
>> ---
>> drivers/iommu/amd_iommu.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
>> index 27eb0d6fcdc2..bb3ef33e3784 100644
>> --- a/drivers/iommu/amd_iommu.c
>> +++ b/drivers/iommu/amd_iommu.c
>> @@ -3271,7 +3271,7 @@ static void amd_iommu_apply_resv_region(struct device *dev,
>> unsigned long start, end;
>>
>> start = IOVA_PFN(region->start);
>> - end = IOVA_PFN(region->start + region->length);
>> + end = IOVA_PFN(region->start + region->length - 1);
>>
>> WARN_ON_ONCE(reserve_iova(&dma_dom->iovad, start, end) == NULL);
>> }
>
> This looks like a fix, should we include:
>
> Fixes: 8d54d6c8b8f3 ('iommu/amd: Implement apply_dm_region call-back')
It turns out there are other places where the computation is incorrect.
Would you prefer a single patch to address all of them, or separate
patches that apply to specific areas of the driver?
prev parent reply other threads:[~2017-10-27 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 21:22 Gary R Hook
2017-10-26 8:32 ` Alex Williamson
2017-10-27 15:20 ` Gary R Hook [this message]
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=df434365-6972-f87c-c77b-f0008aa2b1c8@amd.com \
--to=gary.hook@amd.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®