From: patchwork-bot+netdevbpf@kernel.org
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
richardcochran@gmail.com
Subject: Re: [PATCH] ptp: Fix possible memory leak in ptp_clock_register()
Date: Wed, 20 Oct 2021 13:50:14 +0000 [thread overview]
Message-ID: <163473781494.13902.12873542605821488682.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211020081834.2952888-1-yangyingliang@huawei.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 20 Oct 2021 16:18:34 +0800 you wrote:
> I got memory leak as follows when doing fault injection test:
>
> unreferenced object 0xffff88800906c618 (size 8):
> comm "i2c-idt82p33931", pid 4421, jiffies 4294948083 (age 13.188s)
> hex dump (first 8 bytes):
> 70 74 70 30 00 00 00 00 ptp0....
> backtrace:
> [<00000000312ed458>] __kmalloc_track_caller+0x19f/0x3a0
> [<0000000079f6e2ff>] kvasprintf+0xb5/0x150
> [<0000000026aae54f>] kvasprintf_const+0x60/0x190
> [<00000000f323a5f7>] kobject_set_name_vargs+0x56/0x150
> [<000000004e35abdd>] dev_set_name+0xc0/0x100
> [<00000000f20cfe25>] ptp_clock_register+0x9f4/0xd30 [ptp]
> [<000000008bb9f0de>] idt82p33_probe.cold+0x8b6/0x1561 [ptp_idt82p33]
>
> [...]
Here is the summary with links:
- ptp: Fix possible memory leak in ptp_clock_register()
https://git.kernel.org/netdev/net/c/4225fea1cb28
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-10-20 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 8:18 [PATCH] ptp: Fix possible memory leak in ptp_clock_register() Yang Yingliang
2021-10-20 13:50 ` patchwork-bot+netdevbpf [this message]
2021-10-20 14:21 ` Jakub Kicinski
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=163473781494.13902.12873542605821488682.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox