From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Carpenter Subject: Re: [patch] drm/exynos: potential use after free in exynos_drm_open() Date: Tue, 21 Jan 2014 16:35:56 +0300 Message-ID: <20140121133556.GY7444@mwanda> References: <20140121065748.GC31535@elgon.mountain> <52DE69F3.9070307@bfs.de> <52DE6B8B.6080304@bfs.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <52DE6B8B.6080304@bfs.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org To: walter harms Cc: Kukjin Kim , kernel-janitors@vger.kernel.org, Seung-Woo Kim , dri-devel@lists.freedesktop.org, Kyungmin Park , linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org List-Id: linux-samsung-soc@vger.kernel.org On Tue, Jan 21, 2014 at 01:43:55PM +0100, walter harms wrote: > > i have just noticed: The function already exits > > 194 static void exynos_drm_postclose(struct drm_device *dev, struct drm_file *file) > 195 { > 196 if (!file->driver_priv) > 197 return; > 198 > 199 kfree(file->driver_priv); > 200 file->driver_priv = NULL; > 201 } The function is different in the current code. I glanced through drm_open_helper() and I don't see that file->driver_priv to NULL is needed anyway... regards, dan carpenter