Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751912AbZGaI4u (ORCPT ); Fri, 31 Jul 2009 04:56:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751577AbZGaI4X (ORCPT ); Fri, 31 Jul 2009 04:56:23 -0400 Received: from mx2.redhat.com ([66.187.237.31]:33659 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751097AbZGaI4V (ORCPT ); Fri, 31 Jul 2009 04:56:21 -0400 From: Xiaotian Feng To: airlied@linux.ie, dri-devel@lists.sourceforge.net Cc: linux-kernel@vger.kernel.org Subject: [PATCH 0/4] gpu/drm: fix memory leak when radeon_driver_load_kms fails Date: Fri, 31 Jul 2009 16:55:54 +0800 Message-Id: <1249030558-24143-1-git-send-email-dfeng@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 737 Lines: 15 I've noticed a bundle of kmemleak reports on drm. When I look into dmesg, I found: "[drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon, disabling IOCTL". In radeon_driver_load_kms, if radeon_device_init fails, rdev is not freed. Then radeon_driver_load_kms as dev->driver->load, if load fails in drm_get_dev, memories allocated in drm_fill_in_dev will not be freed. This patchset fixes those memory leaks, after this patchset applied, I didn't see those drm kmemleak report. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/