From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: vkoul@kernel.org, dmaengine@vger.kernel.org,
John David Anglin <dave.anglin@bell.net>,
hch@lst.de, linux-arm-kernel@lists.infradead.org
Subject: dmaengine: mv_xor: Use correct device for DMA API
Date: Tue, 19 Feb 2019 12:02:46 +0100 [thread overview]
Message-ID: <20190219120246.7ed64b2f@windsurf.home> (raw)
Hello Robin,
Thanks a lot for fixing this!
On Mon, 18 Feb 2019 18:27:06 +0000
Robin Murphy <robin.murphy@arm.com> wrote:
> Using dma_dev->dev for mappings before it's assigned with the correct
> device is unlikely to work as expected, and with future dma-direct
> changes, passing a NULL device may end up crashing entirely. I don't
> know enough about this hardware or the mv_xor_prep_dma_interrupt()
> operation to implement the appropriate error-handling logic that would
> have revealed those dma_map_single() calls failing on arm64 for as long
> as the driver has been enabled there, but moving the assignment earlier
> will at least make the current code operate as intended.
>
> Fixes: 22843545b200 ("dma: mv_xor: Add support for DMA_INTERRUPT")
> Reported-by: John David Anglin <dave.anglin@bell.net>
> Tested-by: John David Anglin <dave.anglin@bell.net>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Acked-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Tested-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Best regards,
Thomas
next reply other threads:[~2019-02-19 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 11:02 Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-19 12:10 dmaengine: mv_xor: Use correct device for DMA API Vinod Koul
2019-02-18 18:27 Robin Murphy
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=20190219120246.7ed64b2f@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=dave.anglin@bell.net \
--cc=dmaengine@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robin.murphy@arm.com \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).