[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<169348142263.21678.2348219156838047969.git-patchwork-notify@kernel.org>
Date: Thu, 31 Aug 2023 11:30:22 +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,
jonathan.lemon@...il.com, bpf@...r.kernel.org,
syzbot+822d1359297e2694f873@...kaller.appspotmail.com
Subject: Re: [PATCH bpf v2] xsk: fix xsk_diag use-after-free error during socket
cleanup
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@...earbox.net>:
On Thu, 31 Aug 2023 12:01:17 +0200 you wrote:
> From: Magnus Karlsson <magnus.karlsson@...el.com>
>
> Fix a use-after-free error that is possible if the xsk_diag interface
> is used after the socket has been unbound from the device. This can
> happen either due to the socket being closed or the device
> disappearing. In the early days of AF_XDP, the way we tested that a
> socket was not bound to a device was to simply check if the netdevice
> pointer in the xsk socket structure was NULL. Later, a better system
> was introduced by having an explicit state variable in the xsk socket
> struct. For example, the state of a socket that is on the way to being
> closed and has been unbound from the device is XSK_UNBOUND.
>
> [...]
Here is the summary with links:
- [bpf,v2] xsk: fix xsk_diag use-after-free error during socket cleanup
https://git.kernel.org/bpf/bpf/c/3e019d8a05a3
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