linux-kernel - Re: 2.6.30-rc1: ioatdma: DMA-API: device driver frees DMA memory with wrong function

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 for Android: free password hash cracker in your pocket

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

Message-ID: <e9c3a7c20904151027xdf617fbh64fcb5618e195a71@mail.gmail.com>
Date:	Wed, 15 Apr 2009 10:27:48 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Alexander Beregalov <a.beregalov@...il.com>
Cc:	Kernel Testers List <kernel-testers@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>, maciej.sosnowski@...el.com
Subject: Re: 2.6.30-rc1: ioatdma: DMA-API: device driver frees DMA memory with 
	wrong function

On Wed, Apr 15, 2009 at 5:39 AM, Alexander Beregalov
<a.beregalov@...il.com> wrote:
> 2009/4/9 Alexander Beregalov <a.beregalov@...il.com>:
>> ioatdma 0000:00:08.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>> ioatdma 0000:00:08.0: setting latency timer to 64
>> ioatdma 0000:00:08.0: Intel(R) I/OAT DMA Engine found, 4 channels,
>> device version 0x12, driver version 3.64
>>  alloc irq_desc for 33 on cpu 0 node 0
>>  alloc kstat_irqs on cpu 0 node 0
>> ioatdma 0000:00:08.0: irq 33 for MSI/MSI-X
>> ------------[ cut here ]------------
>> WARNING: at lib/dma-debug.c:565 check_unmap+0x2f6/0x6a0()
>> Hardware name: PowerEdge 1950
>> ioatdma 0000:00:08.0: DMA-API: device driver frees DMA memory with
>> wrong function [device address=0x000000007f76f800] [size=2000 bytes]
>> [map
>> ped as single] [unmapped as page]
>
> The problem still persists.

Thanks for the report Alexander.  Maciej and I are looking into a fix.

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/