From: patchwork-bot+netdevbpf@kernel.org
To: Fijalkowski@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Maciej <maciej.fijalkowski@intel.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, netdev@vger.kernel.org,
magnus.karlsson@intel.com, bjorn@kernel.org,
jordyzomer@google.com, security@kernel.org
Subject: Re: [PATCH v2 bpf 0/2] bpf: fix OOB accesses in map_delete_elem callbacks
Date: Mon, 25 Nov 2024 22:30:36 +0000 [thread overview]
Message-ID: <173257383699.4058254.11460936929624006361.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241122121030.716788-1-maciej.fijalkowski@intel.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 22 Nov 2024 13:10:28 +0100 you wrote:
> v1->v2:
> - CC stable and collect tags from Toke & John
>
> Hi,
>
> Jordy reported that for big enough XSKMAPs and DEVMAPs, when deleting
> elements, OOB writes occur.
>
> [...]
Here is the summary with links:
- [v2,bpf,1/2] xsk: fix OOB map writes when deleting elements
https://git.kernel.org/bpf/bpf/c/32cd3db7de97
- [v2,bpf,2/2] bpf: fix OOB devmap writes when deleting elements
https://git.kernel.org/bpf/bpf/c/ab244dd7cf4c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-11-25 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 12:10 [PATCH v2 bpf 0/2] bpf: fix OOB accesses in map_delete_elem callbacks Maciej Fijalkowski
2024-11-22 12:10 ` [PATCH v2 bpf 1/2] xsk: fix OOB map writes when deleting elements Maciej Fijalkowski
2024-11-22 12:10 ` [PATCH v2 bpf 2/2] bpf: fix OOB devmap " Maciej Fijalkowski
2024-11-25 22:30 ` patchwork-bot+netdevbpf [this message]
2024-11-30 0:43 ` [PATCH v2 bpf 0/2] bpf: fix OOB accesses in map_delete_elem callbacks Cong Wang
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=173257383699.4058254.11460936929624006361.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Fijalkowski@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jordyzomer@google.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=security@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox