From: patchwork-bot+netdevbpf@kernel.org
To: Davide Caratti <dcaratti@redhat.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net resend 0/2] fix stack OOB read while fragmenting IPv4 packets
Date: Thu, 29 Apr 2021 22:40:10 +0000 [thread overview]
Message-ID: <161973601028.15907.1699024796278248158.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1619615320.git.dcaratti@redhat.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Wed, 28 Apr 2021 15:23:00 +0200 you wrote:
> - patch 1/2 fixes openvswitch IPv4 fragmentation, that does a stack OOB
> read after commit d52e5a7e7ca4 ("ipv4: lock mtu in fnhe when received
> PMTU < net.ipv4.route.min_pmt")
> - patch 2/2 fixes the same issue in TC 'sch_frag' code
>
> Davide Caratti (2):
> openvswitch: fix stack OOB read while fragmenting IPv4 packets
> net/sched: sch_frag: fix stack OOB read while fragmenting IPv4 packets
>
> [...]
Here is the summary with links:
- [net,resend,1/2] openvswitch: fix stack OOB read while fragmenting IPv4 packets
https://git.kernel.org/netdev/net/c/7c0ea5930c1c
- [net,resend,2/2] net/sched: sch_frag: fix stack OOB read while fragmenting IPv4 packets
https://git.kernel.org/netdev/net/c/31fe34a0118e
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-04-29 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 13:23 [PATCH net resend 0/2] fix stack OOB read while fragmenting IPv4 packets Davide Caratti
2021-04-28 13:23 ` [PATCH net resend 1/2] openvswitch: " Davide Caratti
2021-04-28 13:23 ` [PATCH net resend 2/2] net/sched: sch_frag: " Davide Caratti
2021-04-29 22:40 ` 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=161973601028.15907.1699024796278248158.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.