netdev - Re: [PATCH v7 bpf-next 0/7] bpf: udp: Exactly-once socket iteration

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] [thread-next>] [day] [month] [year] [list]

Message-Id: 
 <174622083850.3731637.6479069584548815355.git-patchwork-notify@kernel.org>
Date: Fri, 02 May 2025 21:20:38 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jordan Rife <jordan@...fe.io>
Cc: netdev@...r.kernel.org, bpf@...r.kernel.org, aditi.ghag@...valent.com,
 daniel@...earbox.net, martin.lau@...ux.dev, willemdebruijn.kernel@...il.com,
 kuniyu@...zon.com, alexei.starovoitov@...il.com
Subject: Re: [PATCH v7 bpf-next 0/7] bpf: udp: Exactly-once socket iteration

Hello:

This series was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau <martin.lau@...nel.org>:

On Fri,  2 May 2025 09:15:19 -0700 you wrote:
> Both UDP and TCP socket iterators use iter->offset to track progress
> through a bucket, which is a measure of the number of matching sockets
> from the current bucket that have been seen or processed by the
> iterator. On subsequent iterations, if the current bucket has
> unprocessed items, we skip at least iter->offset matching items in the
> bucket before adding any remaining items to the next batch. However,
> iter->offset isn't always an accurate measure of "things already seen"
> when the underlying bucket changes between reads which can lead to
> repeated or skipped sockets. Instead, this series remembers the cookies
> of the sockets we haven't seen yet in the current bucket and resumes
> from the first cookie in that list that we can find on the next
> iteration. This series focuses on UDP socket iterators, but a later
> series will apply a similar approach to TCP socket iterators.
> 
> [...]

Here is the summary with links:
  - [v7,bpf-next,1/7] bpf: udp: Make mem flags configurable through bpf_iter_udp_realloc_batch
    (no matching commit)
  - [v7,bpf-next,2/7] bpf: udp: Make sure iter->batch always contains a full bucket snapshot
    https://git.kernel.org/bpf/bpf-next/c/66d454e99d71
  - [v7,bpf-next,3/7] bpf: udp: Get rid of st_bucket_done
    https://git.kernel.org/bpf/bpf-next/c/3fae8959cda5
  - [v7,bpf-next,4/7] bpf: udp: Use bpf_udp_iter_batch_item for bpf_udp_iter_state batch items
    (no matching commit)
  - [v7,bpf-next,5/7] bpf: udp: Avoid socket skips and repeats during iteration
    (no matching commit)
  - [v7,bpf-next,6/7] selftests/bpf: Return socket cookies from sock_iter_batch progs
    https://git.kernel.org/bpf/bpf-next/c/4a0614e18c2d
  - [v7,bpf-next,7/7] selftests/bpf: Add tests for bucket resume logic in UDP socket iterators
    https://git.kernel.org/bpf/bpf-next/c/c58dcc1dbe30

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