netdev - Re: [PATCH v2 bpf] selftests/bpf: work-around EBUSY errors from hashmap update/delete

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <160877040644.1898.11857535496181994978.git-patchwork-notify@kernel.org>
Date:   Thu, 24 Dec 2020 00:40:06 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Andrii Nakryiko <andrii@...nel.org>
Cc:     bpf@...r.kernel.org, netdev@...r.kernel.org, ast@...com,
        daniel@...earbox.net, kernel-team@...com, songliubraving@...com
Subject: Re: [PATCH v2 bpf] selftests/bpf: work-around EBUSY errors from hashmap
 update/delete

Hello:

This patch was applied to bpf/bpf.git (refs/heads/master):

On Wed, 23 Dec 2020 12:06:52 -0800 you wrote:
> 20b6cc34ea74 ("bpf: Avoid hashtab deadlock with map_locked") introduced
> a possibility of getting EBUSY error on lock contention, which seems to happen
> very deterministically in test_maps when running 1024 threads on low-CPU
> machine. In libbpf CI case, it's a 2 CPU VM and it's hitting this 100% of the
> time. Work around by retrying on EBUSY (and EAGAIN, while we are at it) after
> a small sleep. sched_yield() is too agressive and fails even after 20 retries,
> so I went with usleep(1) for backoff.
> 
> [...]

Here is the summary with links:
  - [v2,bpf] selftests/bpf: work-around EBUSY errors from hashmap update/delete
    https://git.kernel.org/bpf/bpf/c/11b844b0b7c7

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html