All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: netdev@vger.kernel.org, isdn@linux-pingi.de, davem@davemloft.net
Subject: Re: [PATCH net] mISDN: fix possible memory leak in mISDN_dsp_element_register()
Date: Sat, 12 Nov 2022 05:10:17 +0000	[thread overview]
Message-ID: <166822981733.20406.7244212929939531395.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221109132832.3270119-1-yangyingliang@huawei.com>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 9 Nov 2022 21:28:32 +0800 you wrote:
> Afer commit 1fa5ae857bb1 ("driver core: get rid of struct device's
> bus_id string array"), the name of device is allocated dynamically,
> use put_device() to give up the reference, so that the name can be
> freed in kobject_cleanup() when the refcount is 0.
> 
> The 'entry' is going to be freed in mISDN_dsp_dev_release(), so the
> kfree() is removed. list_del() is called in mISDN_dsp_dev_release(),
> so it need be intialized.
> 
> [...]

Here is the summary with links:
  - [net] mISDN: fix possible memory leak in mISDN_dsp_element_register()
    https://git.kernel.org/netdev/net/c/98a2ac1ca8fd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2022-11-12  5:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 13:28 [PATCH net] mISDN: fix possible memory leak in mISDN_dsp_element_register() Yang Yingliang
2022-11-12  5:10 ` patchwork-bot+netdevbpf [this message]

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=166822981733.20406.7244212929939531395.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=isdn@linux-pingi.de \
    --cc=netdev@vger.kernel.org \
    --cc=yangyingliang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.