linux-kernel - Re: [PATCH] dmaengine: pl330: Fix overflow when reporting residue in memcpy

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, 7 Jul 2015 09:28:25 +0530
From:	Vinod Koul <vinod.koul@...el.com>
To:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
Cc:	Dan Williams <dan.j.williams@...el.com>, dmaengine@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	stable@...r.kernel.org
Subject: Re: [PATCH] dmaengine: pl330: Fix overflow when reporting residue in
 memcpy

On Mon, Jun 15, 2015 at 05:25:16PM +0900, Krzysztof Kozlowski wrote:
> During memcpy operations the residue was always set to an u32 overflowed
> value.
> 
> In pl330_tx_status() function number of currently transferred bytes was
> subtracted from internal "bytes_requested" field. However this
> "bytes_requested" was not initialized at start to length of memcpy
> buffer so transferred bytes were subtracted from 0 causing overflow.

Applied, thanks

-- 
~Vinod
--
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/