From: patchwork-bot+netdevbpf@kernel.org
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net 0/3] amt: fix several bugs in amt_rcv()
Date: Mon, 06 Jun 2022 22:04:29 +0000 [thread overview]
Message-ID: <165455306916.27266.12709601246061615305.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220602140108.18329-1-ap420073@gmail.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 2 Jun 2022 14:01:05 +0000 you wrote:
> This series fixes bugs in amt_rcv().
>
> First patch fixes pskb_may_pull() issue.
> Some functions missed to call pskb_may_pull() and uses wrong
> parameter of pskb_may_pull().
>
> Second patch fixes possible null-ptr-deref in amt_rcv().
> If there is no amt private data in sock, skb will be freed.
> And it increases stats.
> But in order to increase stats, amt private data is needed.
> So, uninitialised pointer will be used at that point.
>
> [...]
Here is the summary with links:
- [net,1/3] amt: fix wrong usage of pskb_may_pull()
https://git.kernel.org/netdev/net/c/f55a07074fdd
- [net,2/3] amt: fix possible null-ptr-deref in amt_rcv()
https://git.kernel.org/netdev/net/c/d16207f92a4a
- [net,3/3] amt: fix wrong type string definition
https://git.kernel.org/netdev/net/c/d7970039d87c
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:[~2022-06-06 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 14:01 [PATCH net 0/3] amt: fix several bugs in amt_rcv() Taehee Yoo
2022-06-02 14:01 ` [PATCH net 1/3] amt: fix wrong usage of pskb_may_pull() Taehee Yoo
2022-06-02 14:01 ` [PATCH net 2/3] amt: fix possible null-ptr-deref in amt_rcv() Taehee Yoo
2022-06-02 14:01 ` [PATCH net 3/3] amt: fix wrong type string definition Taehee Yoo
2022-06-06 22:04 ` 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=165455306916.27266.12709601246061615305.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).