On 2019-02-14 12:58 p.m., Robin Murphy wrote:
> Hmm, having felt brave enough to take a closer look, it might actually be as
> simple as this - Dave, are you able to give the diff below a spin?
>
> Robin.
>
> ->8-
> diff --git a/drivers/dma/mv_xor.c b/drivers/dma/mv_xor.c
> index
On 2019-02-15 10:22 a.m., John David Anglin wrote:
> On 2019-02-14 12:58 p.m., Robin Murphy wrote:
>> Hmm, having felt brave enough to take a closer look, it might actually be as
>> simple as this - Dave, are you able to give the diff below a spin?
> Still crashes but in slightly different spot:
On 2019-02-14 12:58 p.m., Robin Murphy wrote:
> Hmm, having felt brave enough to take a closer look, it might actually be as
> simple as this - Dave, are you able to give the diff below a spin?
Still crashes but in slightly different spot:
[ 0.00] Booting Linux on physical CPU
On 2019-02-14 12:58 p.m., Robin Murphy wrote:
> Hmm, having felt brave enough to take a closer look, it might actually be as
> simple as this - Dave, are you able to give the diff below a spin?
Yes.
--
John David Anglin dave.ang...@bell.net
___
On 14/02/2019 17:36, Christoph Hellwig wrote:
On Thu, Feb 14, 2019 at 05:27:41PM +, Robin Murphy wrote:
Oh wow, that driver has possibly the most inventive way of passing a NULL
device to the DMA API that I've ever seen, and on arm64 it will certainly
have been failing since 4.2, but of
On Thu, Feb 14, 2019 at 05:27:41PM +, Robin Murphy wrote:
> Oh wow, that driver has possibly the most inventive way of passing a NULL
> device to the DMA API that I've ever seen, and on arm64 it will certainly
> have been failing since 4.2, but of course there's also no error checking
> for
