From: Leon Romanovsky <leon@kernel.org>
To: Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: michael.chan@broadcom.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
gospo@broadcom.com, netdev@vger.kernel.org
Subject: Re: [PATCH net] bnxt_en: Remove debugfs when pci_register_driver failed
Date: Sun, 13 Nov 2022 10:02:34 +0200 [thread overview]
Message-ID: <Y3Ckmiael4/RsT21@unreal> (raw)
In-Reply-To: <20221111070433.3498215-1-cuigaosheng1@huawei.com>
On Fri, Nov 11, 2022 at 03:04:33PM +0800, Gaosheng Cui wrote:
> When pci_register_driver failed, we need to remove debugfs,
> which will caused a resource leak, fix it.
>
> Resource leak logs as follows:
> [ 52.184456] debugfs: Directory 'bnxt_en' with parent '/' already present!
>
> Fixes: cabfb09d87bd ("bnxt_en: add debugfs support for DIM")
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
> ---
> drivers/net/ethernet/broadcom/bnxt/bnxt.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> index 743504a27b71..0fe164b42c5d 100644
> --- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> @@ -14059,8 +14059,16 @@ static struct pci_driver bnxt_pci_driver = {
>
> static int __init bnxt_init(void)
> {
> + int err;
> +
> bnxt_debug_init();
> - return pci_register_driver(&bnxt_pci_driver);
> + err = pci_register_driver(&bnxt_pci_driver);
> + if (err) {
> + bnxt_debug_exit();
> + return err;
> + }
> +
> + return 0;
> }
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2022-11-13 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 7:04 [PATCH net] bnxt_en: Remove debugfs when pci_register_driver failed Gaosheng Cui
2022-11-13 8:02 ` Leon Romanovsky [this message]
2022-11-13 19:25 ` Michael Chan
2022-11-14 11:00 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y3Ckmiael4/RsT21@unreal \
--to=leon@kernel.org \
--cc=cuigaosheng1@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gospo@broadcom.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).