[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170825065801.GT3053@localhost>
Date: Fri, 25 Aug 2017 12:28:01 +0530
From: Vinod Koul <vinod.koul@...el.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
Cc: Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Niklas Söderlund
<niklas.soderlund+renesas@...natech.se>,
Dan Williams <dan.j.williams@...el.com>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Linux-Kernel <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
Anton Volkov <avolkov@...ras.ru>,
Alexey Khoroshilov <khoroshilov@...ras.ru>,
ldv-project@...uxtesting.org, dmaengine@...r.kernel.org,
geert+renesas@...der.be
Subject: Re: [PATCH v2] rcar-dmac: initialize all data before registering IRQ
handler
On Mon, Aug 21, 2017 at 06:31:57AM +0000, Kuninori Morimoto wrote:
>
> From: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
>
> Anton Volkov noticed that engine->dev is NULL before
> of_dma_controller_register() in probe.
> Thus there might be a NULL pointer dereference in
> rcar_dmac_chan_start_xfer while accessing chan->chan.device->dev which
> is equal to (&dmac->engine)->dev.
> On same reason, same and similar things will happen if we didn't
> initialize all necessary data before calling register irq function.
> To be more safety code, this patch initialize all necessary data
> before calling register irq function.
Applied after adding subsytem name, thanks
--
~Vinod
Powered by blists - more mailing lists