From: Vinod Koul <vinod.koul@intel.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] dmaengine: pl330: Fix overflow when reporting residue in memcpy
Date: Tue, 7 Jul 2015 09:28:25 +0530 [thread overview]
Message-ID: <20150707035825.GE11002@localhost> (raw)
In-Reply-To: <1434356716-32726-1-git-send-email-k.kozlowski@samsung.com>
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
prev parent reply other threads:[~2015-07-07 3:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 8:25 [PATCH] dmaengine: pl330: Fix overflow when reporting residue in memcpy Krzysztof Kozlowski
2015-07-07 3:58 ` Vinod Koul [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150707035825.GE11002@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox