linux-kernel - Re: [PATCH] dmaengine: avoid map_cnt overflow with CONFIG_DMA_ENGINE

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: <20180205053925.GQ18649@localhost>
Date:   Mon, 5 Feb 2018 11:09:25 +0530
From:   Vinod Koul <vinod.koul@...el.com>
To:     Zi Yan <zi.yan@...t.com>
Cc:     dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org,
        Zi Yan <zi.yan@...rutgers.edu>,
        Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCH] dmaengine: avoid map_cnt overflow with
 CONFIG_DMA_ENGINE_RAID

On Mon, Jan 08, 2018 at 10:50:50AM -0500, Zi Yan wrote:
> From: Zi Yan <zi.yan@...rutgers.edu>
> 
> When CONFIG_DMA_ENGINE_RAID is enabled, unmap pool size can reach to
> 256. But in struct dmaengine_unmap_data, map_cnt is only u8, wrapping
> to 0, if the unmap pool is maximally used. This triggers BUG() when
> struct dmaengine_unmap_data is freed. Use u16 to fix the problem.

Applied, thanks

-- 
~Vinod