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] [day] [month] [year] [list]

Message-ID: <4C48BF90.3050100@intel.com>
Date:	Thu, 22 Jul 2010 15:00:48 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Chris Li <lkml@...isli.org>
CC:	David Woodhouse <dwmw2@...radead.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: BUG in drivers/dma/ioat/dma_v2.c:314

On 7/22/2010 2:39 PM, Chris Li wrote:
> On Wed, Jul 21, 2010 at 6:15 PM, Dan Williams<dan.j.williams@...el.com>  wrote:
>>
>> Here is v5 with the aforementioned change.
>
> One warning.
>
> CC      drivers/pci/intel-iommu.o
> drivers/pci/intel-iommu.c: In function ‘quirk_ioat_snb_local_iommu’:
> drivers/pci/intel-iommu.c:3037: warning: unused variable ‘i’

Oops, I'll clean that up.

> The dmesg looks good.
>
[..]
> dca service started, version 1.12.1
> ioatdma: Intel(R) QuickData Technology Driver 4.00
> ioatdma 0000:00:0f.0: can't derive routing for PCI INT A
> ioatdma 0000:00:0f.0: PCI INT A: no GSI
> ------------[ cut here ]------------
> WARNING: at drivers/pci/intel-iommu.c:3056
> quirk_ioat_snb_local_iommu+0xae/0xc7()
> Hardware name: MacPro3,1
> BIOS assigned incorrect VT-d unit for Intel(R) QuickData Technology device
[..]
> ---[ end trace c7f418b83f8ca665 ]---
> Disabling lock debugging due to kernel taint
> ioatdma 0000:00:0f.0: setting latency timer to 64
>    alloc irq_desc for 57 on node -1
>    alloc kstat_irqs on node -1
> ioatdma 0000:00:0f.0: irq 57 for MSI/MSI-X
>    alloc irq_desc for 58 on node -1
>    alloc kstat_irqs on node -1
> ioatdma 0000:00:0f.0: irq 58 for MSI/MSI-X
>    alloc irq_desc for 59 on node -1
>    alloc kstat_irqs on node -1
> ioatdma 0000:00:0f.0: irq 59 for MSI/MSI-X
>    alloc irq_desc for 60 on node -1
>    alloc kstat_irqs on node -1
> ioatdma 0000:00:0f.0: irq 60 for MSI/MSI-X
>

Nice, and the driver was able to load normally.  Thanks for the all the 
testing!

David, I'll take this through my tree as a regression fix (since 2.6.32) 
if you have no objections.  Now that we are not hitting a driver load 
failure I think I'll add a WARN() to this init-fail path.  I doubt we 
would have flushed out this problem had the driver been discretely 
handling init failures since day one.

Regards,
Dan
--
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/