linux-kernel - Re: DMAR:[fault reason 02] Present bit in context entry is clear (firewire-ohci)

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]

Message-ID: <20111119172127.GA31915@nomi.cz>
Date:	Sat, 19 Nov 2011 18:21:27 +0100
From:	Tomáš Janoušek <tomi@...i.cz>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	Matthew Wilcox <matthew@....cx>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux-pci@...r.kernel.org, linux1394-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org,
	Dominik Brodowski <linux@...inikbrodowski.net>
Subject: Re: DMAR:[fault reason 02] Present bit in context entry is clear
	(firewire-ohci)

Hello guys,

On Sat, May 22, 2010 at 12:09:05PM -0700, Jesse Barnes wrote:
> On Sat, 22 May 2010 19:40:43 +0100
> David Woodhouse <dwmw2@...radead.org> wrote:
> > [...]
> > Yeah, the DMAR looks at the source-id in the PCIe transactions, and it
> > sounds like those are all 04:00.0. But we've probably set up the DMAR to
> > allow the transactions from 04:00.4, and then it naturally faults when a
> > "different" device actually ends up doing the transaction.
> > 
> > If you make the pci_find_upstream_pcie_bridge() function do the
> > appropriate thing for this device, does it then work as expected?
> > 
> > Whether that's a _sane_ thing to do or not is possibly more of a Jesse
> > question...
> 
> Well, if cardbus bridges tend to behave this way in general it would
> make sense to simply use the cardbus bride id everywhere, rather than
> the specific functions of the device.  Cc'ing Dominik.

Any news on this one? It is still an issue with current kernel on current
hardware (like my ThinkPad T420). :-(

Regards,
-- 
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/
--
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/