public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Kuniyuki Iwashima <kuniyu@amazon•com>
Cc: davem@davemloft•net, dsahern@kernel•org, edumazet@google•com,
	kuba@kernel•org, pabeni@redhat•com, lorenzo@google•com,
	benh@amazon•com, ayudutta@amazon•com, netdev@vger•kernel.org,
	syzbot+a8430774139ec3ab7176@syzkaller•appspotmail.com
Subject: Re: [PATCH v2 net] net: ping6: Fix memleak in ipv6_renew_options().
Date: Thu, 28 Jul 2022 18:10:13 +0000	[thread overview]
Message-ID: <165903181374.2291.8213182596118662690.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220728012220.46918-1-kuniyu@amazon.com>

Hello:

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

On Wed, 27 Jul 2022 18:22:20 -0700 you wrote:
> When we close ping6 sockets, some resources are left unfreed because
> pingv6_prot is missing sk->sk_prot->destroy().  As reported by
> syzbot [0], just three syscalls leak 96 bytes and easily cause OOM.
> 
>     struct ipv6_sr_hdr *hdr;
>     char data[24] = {0};
>     int fd;
> 
> [...]

Here is the summary with links:
  - [v2,net] net: ping6: Fix memleak in ipv6_renew_options().
    https://git.kernel.org/netdev/net/c/e27326009a3d

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



      parent reply	other threads:[~2022-07-28 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28  1:22 [PATCH v2 net] net: ping6: Fix memleak in ipv6_renew_options() Kuniyuki Iwashima
2022-07-28  3:11 ` Jakub Kicinski
2022-07-28 16:13 ` David Ahern
2022-07-28 16:50 ` Eric Dumazet
2022-07-28 18: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=165903181374.2291.8213182596118662690.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=ayudutta@amazon$(echo .)com \
    --cc=benh@amazon$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dsahern@kernel$(echo .)org \
    --cc=edumazet@google$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=kuniyu@amazon$(echo .)com \
    --cc=lorenzo@google$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=syzbot+a8430774139ec3ab7176@syzkaller$(echo .)appspotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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