From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
kuni1840@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net 0/3] fou/gue: Fix skb memleak with inner protocol 0.
Date: Mon, 19 Jan 2026 14:18:31 +0000 [thread overview]
Message-ID: <176883231127.1426077.10009539879991109915.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260115172533.693652-1-kuniyu@google.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 15 Jan 2026 17:24:45 +0000 you wrote:
> syzbot reported memleak for a GUE packet with its inner
> protocol number 0.
>
> Patch 1 fixes the issue, and patch 3 fixes the same issue
> in FOU.
>
>
> [...]
Here is the summary with links:
- [v2,net,1/3] gue: Fix skb memleak with inner IP protocol 0.
https://git.kernel.org/netdev/net/c/9a56796ad258
- [v2,net,2/3] tools: ynl: Specify --no-line-number in ynl-regen.sh.
https://git.kernel.org/netdev/net/c/68578370f9b3
- [v2,net,3/3] fou: Don't allow 0 for FOU_ATTR_IPPROTO.
https://git.kernel.org/netdev/net/c/7a9bc9e3f423
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:[~2026-01-19 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 17:24 [PATCH v2 net 0/3] fou/gue: Fix skb memleak with inner protocol 0 Kuniyuki Iwashima
2026-01-15 17:24 ` [PATCH v2 net 1/3] gue: Fix skb memleak with inner IP " Kuniyuki Iwashima
2026-01-15 17:24 ` [PATCH v2 net 2/3] tools: ynl: Specify --no-line-number in ynl-regen.sh Kuniyuki Iwashima
2026-01-15 17:31 ` Eric Dumazet
2026-01-15 17:24 ` [PATCH v2 net 3/3] fou: Don't allow 0 for FOU_ATTR_IPPROTO Kuniyuki Iwashima
2026-01-15 17:27 ` Eric Dumazet
2026-01-19 14:18 ` 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=176883231127.1426077.10009539879991109915.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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