linux-kernel - Re: git-latest: kernel oops in IOMMU setup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 8 Jan 2009 13:56:25 -0800
From:	Dirk Hohndel <hohndel@...radead.org>
To:	Grant Grundler <grundler@...isc-linux.org>
Cc:	Ingo Molnar <mingo@...e.hu>, iommu@...ts.linux-foundation.org,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: git-latest: kernel oops in IOMMU setup

On Thu, 8 Jan 2009 14:41:16 -0700
Grant Grundler <grundler@...isc-linux.org> wrote:

> On Thu, Jan 08, 2009 at 12:05:38PM -0800, Dirk Hohndel wrote:
> > 
> > latest git from Linus. On a Thinkpad x200s with VT-d enabled (if I
> > disable VT-d, this of course goes away). 
> > 
> > The oops happens very early during boot in device_to_iommu (called
> > from domain_context_mapping_one).

Look here, that's where it's called from.
Do you want me to note down the complete backtrace?


> If you can, a back trace. Basically just need to know which caller
> is tripping over this. But there can't be that many callers and they
> are all in this file:
> ...
> so it should be possible to figure out which one is called
> before the dev is setup. It's unlikely to be anything with
> "remove" in the name. :)

correct - it's context_mapping_one

-- 
Dirk Hohndel
Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/