linux-kernel - Re: BUG in drivers/dma/ioat/dma

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: <AANLkTimToKAxKLyONyk7KP4WXCS_FpjRjr1yWB3GCaQk@mail.gmail.com>
Date:	Tue, 6 Jul 2010 16:40:21 -0700
From:	Chris Li <lkml@...isli.org>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	"Williams, Dan J" <dan.j.williams@...el.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: BUG in drivers/dma/ioat/dma_v2.c:314

On Mon, Jul 5, 2010 at 3:16 AM, David Woodhouse <dwmw2@...radead.org> wrote:
> On Fri, 2010-07-02 at 20:00 +0100, Chris Li wrote:
>> But I don't see the line that print out BIOS is lying.
>
> Hrm. Want to augment the dmar_find_matched_drhd_unit() function to
> _always_ print the DRHD returned for the offending PCI device? And if
> that still doesn't show, make it print pdev->vendor, pdev->device and
> the returned DRHD pointer for _every_ call?

I just did some experiment, my PCI device ID is  PCI_DEVICE_ID_INTEL_ESB2_0
(0x2670) instead of PCI_DEVICE_ID_INTEL_IOAT_SNB.

That seems to be the reason preventing the warning to be print out. I am not
sure the warning should be always print out. Just curious why it did
not trigger.

Chris
--
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/