From: patchwork-bot+netdevbpf@kernel.org
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+f0bbb2287b8993d4fa74@syzkaller.appspotmail.com
Subject: Re: [PATCH] net: sched: fix memory leak in tcindex_partial_destroy_work
Date: Sun, 18 Jul 2021 16:50:04 +0000 [thread overview]
Message-ID: <162662700498.19662.15454403088763553589.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210717112933.12670-1-paskripkin@gmail.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Sat, 17 Jul 2021 14:29:33 +0300 you wrote:
> Syzbot reported memory leak in tcindex_set_parms(). The problem was in
> non-freed perfect hash in tcindex_partial_destroy_work().
>
> In tcindex_set_parms() new tcindex_data is allocated and some fields from
> old one are copied to new one, but not the perfect hash. Since
> tcindex_partial_destroy_work() is the destroy function for old
> tcindex_data, we need to free perfect hash to avoid memory leak.
>
> [...]
Here is the summary with links:
- net: sched: fix memory leak in tcindex_partial_destroy_work
https://git.kernel.org/netdev/net/c/f5051bcece50
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-07-18 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 11:29 [PATCH] net: sched: fix memory leak in tcindex_partial_destroy_work Pavel Skripkin
2021-07-18 16:50 ` 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=162662700498.19662.15454403088763553589.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paskripkin@gmail.com \
--cc=syzbot+f0bbb2287b8993d4fa74@syzkaller.appspotmail.com \
--cc=xiyou.wangcong@gmail.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