From: Jan Kiszka <jan.kiszka@web.de>
To: Sheng Yang <sheng@linux.intel.com>
Cc: kvm <kvm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Crash in intel_iommu_assign_device
Date: Tue, 02 Nov 2010 08:07:04 +0100 [thread overview]
Message-ID: <4CCFB898.5030200@web.de> (raw)
In-Reply-To: <201011021452.19525.sheng@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Am 02.11.2010 07:52, Sheng Yang wrote:
> On Monday 01 November 2010 19:41:21 Jan Kiszka wrote:
>> Hi Sheng,
>>
>> I'm not claiming to understand the details, but this looks like use
>> (dereference of pte via dma_pte_addr) after release (free_pgtable_page
>> of dmar_domain->pgd aka pte) to me:
>>
>> static int intel_iommu_attach_device(struct iommu_domain *domain,
>> struct device *dev)
>> {
>> [...]
>> pte = dmar_domain->pgd;
>> if (dma_pte_present(pte)) {
>> free_pgtable_page(dmar_domain->pgd);
>> dmar_domain->pgd = (struct dma_pte *)
>> phys_to_virt(dma_pte_addr(pte));
>> }
>>
>> At least it crashes here right on pte->val access. Swap both lines?
>
> I think code is right.
>
> The comment above indicate the case: the code want to decrease the level of page
> table. Mostly it is a 4 level page table, and the code would turn it into 3 levels
> pagetable. What the code did is just get the first entry of the old pagetable level
> 4, then free the level 4 pagetable's page, and make the pagetable to a level 3
> pagetable.
>
> Seems it make no sense to swap the lines...
It fixes the crash here, and I'm convinced the current code is wrong.
See the patch I've just sent out.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
prev parent reply other threads:[~2010-11-02 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 11:41 Crash in intel_iommu_assign_device Jan Kiszka
2010-11-02 6:52 ` Sheng Yang
2010-11-02 7:07 ` Jan Kiszka [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=4CCFB898.5030200@web.de \
--to=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sheng@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.