From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D116CC7EE23 for ; Fri, 26 May 2023 09:03:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242878AbjEZJDO (ORCPT ); Fri, 26 May 2023 05:03:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52076 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236705AbjEZJDN (ORCPT ); Fri, 26 May 2023 05:03:13 -0400 Received: from smtpbgbr1.qq.com (smtpbgbr1.qq.com [54.207.19.206]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A00A512A; Fri, 26 May 2023 02:03:09 -0700 (PDT) X-QQ-mid: Yeas43t1685091710t715t18142 Received: from 3DB253DBDE8942B29385B9DFB0B7E889 (jiawenwu@trustnetic.com [125.120.148.168]) X-QQ-SSF: 00400000000000F0FOF000000000000 From: =?utf-8?b?Smlhd2VuIFd1?= X-BIZMAIL-ID: 2709956065173614677 To: "'Russell King \(Oracle\)'" Cc: "'Jakub Kicinski'" , , , , , , , , , , , References: <20230524091722.522118-1-jiawenwu@trustnetic.com> <20230524091722.522118-9-jiawenwu@trustnetic.com> <20230525211403.44b5f766@kernel.org> <022201d98f9a$4b4ccc00$e1e66400$@trustnetic.com> In-Reply-To: Subject: RE: [PATCH net-next v9 8/9] net: txgbe: Implement phylink pcs Date: Fri, 26 May 2023 17:01:49 +0800 Message-ID: <026901d98fb0$b5001d80$1f005880$@trustnetic.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQIrQcdiCo7tNEhbaUMwQ6r5o07FvQI4H2aIApOsZCcBuMNaNAG5zvSTrobqp4A= Content-Language: zh-cn X-QQ-SENDSIZE: 520 Feedback-ID: Yeas:trustnetic.com:qybglogicsvrgz:qybglogicsvrgz5a-1 Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Friday, May 26, 2023 4:43 PM, Russell King (Oracle) wrote: > On Fri, May 26, 2023 at 02:21:23PM +0800, Jiawen Wu wrote: > > On Friday, May 26, 2023 12:14 PM, Jakub Kicinski wrote: > > > On Wed, 24 May 2023 17:17:21 +0800 Jiawen Wu wrote: > > > > + ret = devm_mdiobus_register(&pdev->dev, mii_bus); > > > > + if (ret) > > > > + return ret; > > > > + > > > > + mdiodev = mdio_device_create(mii_bus, 0); > > > > + if (IS_ERR(mdiodev)) > > > > + return PTR_ERR(mdiodev); > > > > + > > > > + xpcs = xpcs_create(mdiodev, PHY_INTERFACE_MODE_10GBASER); > > > > + if (IS_ERR(xpcs)) { > > > > + mdio_device_free(mdiodev); > > > > + return PTR_ERR(xpcs); > > > > + } > > > > > > How does the mdiodev get destroyed in case of success? > > > Seems like either freeing it in case of xpcs error is unnecessary > > > or it needs to also be freed when xpcs is destroyed? > > > > When xpcs is destroyed, that means mdiodev is no longer needed. > > I think there is no need to free mdiodev in case of xpcs error, > > since devm_* function leads to free it. > > If you are relying on the devm-ness of devm_mdiobus_register() then > it won't. Although mdiobus_unregister() walks bus->mdio_map[], I > think you are assuming that the mdio device you've created in > mdio_device_create() will be in that array. MDIO devices only get > added to that array when mdiobus_register_device() has been called, > which must only be called from mdio_device_register(). > > Please arrange to call mdio_device_free() prior to destroying the > XPCS in every case. Get it.