Received: by 2002:a05:6358:f14:b0:e5:3b68:ec04 with SMTP id b20csp114406rwj; Thu, 22 Dec 2022 21:54:31 -0800 (PST) X-Google-Smtp-Source: AMrXdXvxAc37lfsqW9y02NCzQEZaE3CuotzcWA8qlnTm5PM9Rq2T5FVFayWIh0ZTdfmrwhGMkJAm X-Received: by 2002:a17:906:c192:b0:7c1:6fe:f4a2 with SMTP id g18-20020a170906c19200b007c106fef4a2mr6386048ejz.45.1671774871429; Thu, 22 Dec 2022 21:54:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671774871; cv=none; d=google.com; s=arc-20160816; b=pQFGTch4ZjNwMuaViFxyA/dmiik/bqZ8BttjS6r7TKNlBac2PNrhzabGjjbWcPwpE2 aiaHkfOTE/Nef1DtBEYH1+NjgmAshmrVW4ukIOK+1eWn3qHenjUzeWUTyIoyAKEH49tR eU1txTo+dCa3xyRgpT8EtuoEG/2lB5Pwj25MgBm4ALWsHMMxNv9LXRZQCwnhdgw0dwah KVGO3r2ch78dcUXZENZkJVveoxrwDcz4So2UM98Ph2seQY8aVE1CNpc6NBNyuNNMvZJT hcmBgcYowg22nXpxTs78X2cLBVsFJnLm8aeZiH+aTp9QnCT6DNBYneikdsgYU9RNPOM3 rRXg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=tVJaPPrD1u+bF/z+8Ks5ZUssRPYbU3R1MeWtOyfJBJM=; b=LYHz80/fgzsonPk37ys7bI5vtefH3IgW6S1fML2MvGdz4NefwDjZzxs9NqvJuNI3sU n0TA3g3HsZj9TQ3cQH4wqvHL0FBLrm371WRrwk+1r0h7TBXKXPfYOUsQFg+4nMcM99wF i4YebJwf/Z0Y4Bv5wXzTOlvc2U1KkJmgETwy7yPt0Kb8daqJno6BXR3ZdaDePsj5myDg QPo8yewMSPIa+wTYdlI1ObLNHHpxu4vqsDy7tjl/xHRqfhxplRfMfJOdrRtpnHeAmEGp CuXBaNcrbuN16x2RDDPTYTbqRwh+Ja+4wCEFZnG4MOdOFyyrhWFSIcSkDPrVd9KClkCj Nffg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=pnQNdZrd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hs36-20020a1709073ea400b0073db353cb25si1882550ejc.869.2022.12.22.21.54.15; Thu, 22 Dec 2022 21:54:31 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=pnQNdZrd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229735AbiLWF2t (ORCPT + 68 others); Fri, 23 Dec 2022 00:28:49 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60482 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229524AbiLWF2r (ORCPT ); Fri, 23 Dec 2022 00:28:47 -0500 Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [213.167.242.64]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 729281CB30; Thu, 22 Dec 2022 21:28:45 -0800 (PST) Received: from [IPV6:2401:4900:1f3f:d076:4da6:b729:f032:ed0a] (unknown [IPv6:2401:4900:1f3f:d076:4da6:b729:f032:ed0a]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id C736F93; Fri, 23 Dec 2022 06:28:37 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1671773322; bh=Lew3jrQRHjRkccU+AQDJAFQBxkdZnuSTUagLXbMqiIk=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=pnQNdZrdaRnxHqDRXI7NV3hu+0Ab9FozDptohx38HkRCag0hE1WY//6HScF5/p8CA 1+lj5CkbuJGybjA1Ll+W2tK3wl1bNa+pjZMkLHzpAaMQsh+UVGZ9J0WbgxWv85h74B ww4AbXvhY0REUucqOCdF4JDquO76LzbCcOTlno9Y= Message-ID: <3c864c60-91a6-9ef4-367e-3c8d453b765b@ideasonboard.com> Date: Fri, 23 Dec 2022 10:58:31 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Subject: Re: [PATCH v2 1/4] staging: vc04_services: Stop leaking platform device on error path Content-Language: en-US To: Laurent Pinchart Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, Greg Kroah-Hartman , Adrien Thierry , Stefan Wahren , Florian Fainelli , Dan Carpenter , Nicolas Saenz Julienne , Phil Elwell , Dave Stevenson , Kieran Bingham References: <20221222191500.515795-1-umang.jain@ideasonboard.com> <20221222191500.515795-2-umang.jain@ideasonboard.com> From: Umang Jain In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_PASS, SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 12/23/22 2:00 AM, Laurent Pinchart wrote: > Hi Umang, > > Thank you for the patch. > > On Fri, Dec 23, 2022 at 12:44:57AM +0530, Umang Jain wrote: >> vchiq driver registers the child platform devices in >> vchiq_register_child(). However, in the registration error code path, >> currently the driver is leaking platform devices by not destroying the >> return platform device. Plug this leak using platform_device_put() as >> mentioned in the documentation for platform_device_register(). >> >> Signed-off-by: Umang Jain >> --- >> drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c >> index dc33490ba7fb..fc7ea7ba97b2 100644 >> --- a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c >> +++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c >> @@ -1779,6 +1779,7 @@ vchiq_register_child(struct platform_device *pdev, const char *name) >> child = platform_device_register_full(&pdevinfo); >> if (IS_ERR(child)) { >> dev_warn(&pdev->dev, "%s not registered\n", name); >> + platform_device_put(child); > If IS_ERR(child), what do you expect platform_device_put(child) to do ? > And have you read the implementation of platform_device_register_full() > ? Errr, yeah - it is handling the platform_device_put() as well. Stupid me! (dropping this patch for v3) > >> child = NULL; >> } >>