netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Gilad Naaman <gnaaman@drivenets.com>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
	lschlesinger@drivenets.com
Subject: Re: [PATCH iproute2] libnetlink: Fix memory leak in __rtnl_talk_iov()
Date: Fri, 09 Dec 2022 18:20:17 +0000	[thread overview]
Message-ID: <167061001744.13827.14134499118420494295.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221205084741.3426393-1-gnaaman@drivenets.com>

Hello:

This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:

On Mon,  5 Dec 2022 10:47:41 +0200 you wrote:
> From: Lahav Schlesinger <lschlesinger@drivenets.com>
> 
> If `__rtnl_talk_iov` fails then callers are not expected to free `answer`.
> 
> Currently if `NLMSG_ERROR` was received with an error then the netlink
> buffer was stored in `answer`, while still returning an error
> 
> [...]

Here is the summary with links:
  - [iproute2] libnetlink: Fix memory leak in __rtnl_talk_iov()
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=0faec4d050b6

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



  reply	other threads:[~2022-12-09 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05  8:47 [PATCH iproute2] libnetlink: Fix memory leak in __rtnl_talk_iov() Gilad Naaman
2022-12-09 18:20 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-23 16:15 Gilad Naaman
2022-12-01 16:00 ` Stephen Hemminger

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=167061001744.13827.14134499118420494295.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=gnaaman@drivenets.com \
    --cc=lschlesinger@drivenets.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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).