[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdZ8wquWRNKs=9Y8A8VPuUBB06BH5K4SMsFQr2cBWkZz0w@mail.gmail.com>
Date: Mon, 30 Jan 2017 16:25:21 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
Cc: Shailendra Verma <shailendra.v@...sung.com>,
Laxman Dewangan <ldewangan@...dia.com>,
Andreas Klinger <ak@...klinger.de>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Andrew Lunn <andrew@...n.ch>, Jamie Lentin <jm@...tin.co.uk>,
Rob Herring <robh@...nel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
p.shailesh@...sung.com, ashish.kalra@...sung.com,
Shailendra Verma <shailendra.capricorn@...il.com>
Subject: Re: [PATCH] Pinctrl: mvebu - Fix possible NULL derefrence.
On Mon, Jan 30, 2017 at 9:24 AM, Thomas Petazzoni
<thomas.petazzoni@...e-electrons.com> wrote:
> On Mon, 30 Jan 2017 10:21:43 +0530, Shailendra Verma wrote:
>> of_match_device could return NULL, and so can cause a NULL
>> pointer dereference later.
>>
>> Signed-off-by: Shailendra Verma <shailendra.v@...sung.com>
>
> In practice, I don't see how of_match_device() can return NULL here.
> Indeed, those drivers only support Device Tree based probing, so
> of_match_device() will always return a non-NULL value.
OK you're right, this is too overly cautious.
Saliendra, sorry but I have to drop these patches.
Yours,
Linus Walleij
Powered by blists - more mailing lists