linux-kernel - Re: [4.0-rc+] WARNING: CPU: 0 PID: 1 at ./drivers/dma/dmaengine.c:863 dma_async_device

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150408155945.GG26727@lukather>
Date:	Wed, 8 Apr 2015 17:59:45 +0200
From:	Maxime Ripard <maxime.ripard@...e-electrons.com>
To:	Peter Hurley <peter@...leysoftware.com>
Cc:	Vinod Koul <vinod.koul@...el.com>, Felipe Balbi <balbi@...com>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [4.0-rc+] WARNING: CPU: 0 PID: 1 at
 ./drivers/dma/dmaengine.c:863 dma_async_device_register+0xe0/0x540()

On Wed, Apr 08, 2015 at 11:53:33AM -0400, Peter Hurley wrote:
> On 03/05/2015 11:12 AM, Vinod Koul wrote:
> > On Thu, Mar 05, 2015 at 10:04:21AM -0500, Peter Hurley wrote:
> >> > First boot of 4.0-rc+ gave me [1] on a Beaglebone Black due to
> >> > 
> > The warning is intentional to get driver fixed and give the right behaviour
> > 
> > Felipe had sent a patch for this but that one needs an update
> 
> Vinod,
> 
> Felipe's patch never made it to mainline, and this warning is 
> still happening on 4.0-rc7 so please revert for 4.0-final.

That patch isn't introducing any regression. I fail to see how that
justifies a revert so late in the release cycle.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)