[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<171757383091.23600.1874186480870306313.git-patchwork-notify@kernel.org>
Date: Wed, 05 Jun 2024 07:50:30 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Magnus Karlsson <magnus.karlsson@...il.com>
Cc: magnus.karlsson@...el.com, bjorn@...nel.org, ast@...nel.org,
daniel@...earbox.net, netdev@...r.kernel.org, maciej.fijalkowski@...el.com,
bpf@...r.kernel.org, YuvalE@...ware.com
Subject: Re: [PATCH bpf 0/2] Revert "xsk: support redirect to any socket bound to
the same umem"
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@...earbox.net>:
On Tue, 4 Jun 2024 14:29:24 +0200 you wrote:
> Revert "xsk: support redirect to any socket bound to the same umem"
>
> This patch introduced a potential kernel crash when multiple napi
> instances redirect to the same AF_XDP socket. By removing the
> queue_index check, it is possible for multiple napi instances to
> access the Rx ring at the same time, which will result in a corrupted
> ring state which can lead to a crash when flushing the rings in
> __xsk_flush(). This can happen when the linked list of sockets to
> flush gets corrupted by concurrent accesses. A quick and small fix is
> unfortunately not possible, so let us revert this for now.
>
> [...]
Here is the summary with links:
- [bpf,1/2] Revert "xsk: support redirect to any socket bound to the same umem"
https://git.kernel.org/bpf/bpf/c/7fcf26b315bb
- [bpf,2/2] Revert "xsk: document ability to redirect to any socket bound to the same umem"
https://git.kernel.org/bpf/bpf/c/03e38d315f3c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists