linux-kernel - Re: [PATCH] ioatdma: fix "ioatdma 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 12 May 2009 14:03:25 +0400
From:	Alexander Beregalov <a.beregalov@...il.com>
To:	Maciej Sosnowski <maciej.sosnowski@...el.com>
Cc:	dan.j.williams@...el.com, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH] ioatdma: fix "ioatdma frees DMA memory with wrong 
	function"

2009/4/23 Maciej Sosnowski <maciej.sosnowski@...el.com>:
> as reported by Alexander Beregalov <a.beregalov@...il.com>
>
> 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 ioatdma driver was unmapping all regions
> (either allocated as page or single) using unmap_page.
> This patch lets dma driver recognize if unmap_single or unmap_page should be used.
> It introduces two new dma control flags:
> DMA_COMPL_SRC_UNMAP_SINGLE and DMA_COMPL_DEST_UNMAP_SINGLE.
> They should be set to indicate dma driver to do dma-unmapping as single
> (first one for the source, tha latter for the destination).
> If respective flag is not set, the driver assumes dma-unmapping as page.
>
> Signed-off-by: Maciej Sosnowski <maciej.sosnowski@...el.com>
> Acked-by: Dan Williams <dan.j.williams@...el.com>
> Reported-by: Alexander Beregalov <a.beregalov@...il.com>
> Tested-by: Alexander Beregalov <a.beregalov@...il.com>
> ---

Will it be sent to Linus ?
--
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/