linux-kernel - Re: [dmaengine: shdma] RIP: 0010:[<ffffffff8124ad42>] [<ffffffff8124ad42>] __asan

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: <CAMuHMdXKqT3yTSwnK8LSFS=heXwBZ+46ZONysdSVXGwrBtWivg@mail.gmail.com>
Date:	Mon, 29 Jun 2015 10:37:43 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	kernel test robot <fengguang.wu@...el.com>
Cc:	Geert Uytterhoeven <geert+renesas@...der.be>, LKP <lkp@...org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	dmaengine@...r.kernel.org, Ulf Hansson <ulf.hansson@...aro.org>,
	Vinod Koul <vinod.koul@...el.com>
Subject: Re: [dmaengine: shdma] RIP: 0010:[<ffffffff8124ad42>]
 [<ffffffff8124ad42>] __asan_load8

On Fri, Jun 26, 2015 at 11:47 PM, kernel test robot
<fengguang.wu@...el.com> wrote:
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit b6d1778bc5485c55c6f5194b8b2ea84c0ce5adad
> Author:     Geert Uytterhoeven <geert+renesas@...der.be>
> AuthorDate: Thu Feb 26 11:26:34 2015 +0100
> Commit:     Vinod Koul <vinod.koul@...el.com>
> CommitDate: Mon Mar 2 22:10:44 2015 +0530
>
>     dmaengine: shdma: Move DMA stop to (runtime) suspend callbacks
>
>     During system reboot, the sh-dma-engine device may be runtime-suspended,
>     causing a crash:
>
>         Unhandled fault: imprecise external abort (0x1406) at 0x0002c02c
>         Internal error: : 1406 [#1] SMP ARM
>         ...
>         PC is at sh_dmae_ctl_stop+0x28/0x64
>         LR is at sh_dmae_ctl_stop+0x24/0x64
>
>     If the sh-dma-engine is runtime-suspended, its module clock is turned
>     off, and its registers cannot be accessed.
>
>     To fix this, move the call to sh_dmae_ctl_stop(), which touches the
>     DMAOR register, to the sh_dmae_suspend() and sh_dmae_runtime_suspend()
>     callbacks.  This makes PM operations more symmetric, as both
>     sh_dmae_resume() and sh_dmae_runtime_resume() already call sh_dmae_rst()
>     to re-initialize the DMAOR register.
>
>     Remove sh_dmae_shutdown(), as it became empty.
>
>     Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
>     Reviewed-by: Ulf Hansson <ulf.hansson@...aro.org>
>     Signed-off-by: Vinod Koul <vinod.koul@...el.com>

As the crash is on x86_64, and that commit affects sh/arm only, I'm
afraid your crash is due to an intermittent problem.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
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/