Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Wed, 15 Feb 2023 16:21:30 +0800 you wrote:
> From: Hou Tao <houtao1@xxxxxxxxxx>
>
> Hi,
>
> The patchset tries to fix the hard-up problem found when checking how htab
> handles element reuse in bpf memory allocator. The immediate reuse of
> freed elements will reinitialize special fields (e.g., bpf_spin_lock) in
> htab map value and it may corrupt lookup procedure with BFP_F_LOCK flag
> which acquires bpf-spin-lock during value copying, and lead to hard-lock
> as shown in patch #2. Patch #1 fixes it by using __GFP_ZERO when allocating
> the object from slab and the behavior is similar with the preallocated
> hash-table case. Please see individual patches for more details. And comments
> are always welcome.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Zeroing allocated object from slab in bpf memory allocator
https://git.kernel.org/bpf/bpf-next/c/997849c4b969
- [bpf-next,2/2] selftests/bpf: Add test case for element reuse in htab map
https://git.kernel.org/bpf/bpf-next/c/f88da2d46cc9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
