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: <a4423d670904220848g3725e6a3ya113d9051e2fc734@mail.gmail.com>
Date:	Wed, 22 Apr 2009 19:48:53 +0400
From:	Alexander Beregalov <a.beregalov@...il.com>
To:	"Sosnowski, Maciej" <maciej.sosnowski@...el.com>
Cc:	"Williams, Dan J" <dan.j.williams@...el.com>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.30-rc1: ioatdma: DMA-API: device driver frees DMA memory with 
	wrong function

2009/4/22 Sosnowski, Maciej <maciej.sosnowski@...el.com>:
> Alexander Beregalov wrote:
>> 2009/4/17 Sosnowski, Maciej <maciej.sosnowski@...el.com>:
>>> Dan Williams wrote:
>>>> 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
>>>
>>> Hi Alexander,
>>>
>>> Could you check if the following patch helps?
>>
>> Hi Maciej.
>>
>> No, unfortunately it does not help. The same warning message.
>
> Ok, I have missed to cover self_test case.
> How about this one instead?
>

It works! Thanks.

Reported-by: Alexander Beregalov <a.beregalov@...il.com>
Tested-by: Alexander Beregalov <a.beregalov@...il.com>
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ