Re: [bpf-next PATCH v2 0/6] sockmap/sk_skb program memory acct fixes

Hello:

This series was applied to bpf/bpf-next.git (refs/heads/master):

On Fri, 09 Oct 2020 11:35:53 -0700 you wrote:

Users of sockmap and skmsg trying to build proxys and other tools
have pointed out to me the error handling can be problematic. If
the proxy is under-provisioned and/or the BPF admin does not have
the ability to update/modify memory provisions on the sockets
its possible data may be dropped. For some things we have retries
so everything works out OK, but for most things this is likely
not great. And things go bad.

[...]

Here is the summary with links:
  - [bpf-next,v3,1/6] bpf, sockmap: skb verdict SK_PASS to self already checked rmem limits
    https://git.kernel.org/bpf/bpf-next/c/cfea28f890cf
  - [bpf-next,v3,2/6] bpf, sockmap: On receive programs try to fast track SK_PASS ingress
    https://git.kernel.org/bpf/bpf-next/c/9ecbfb06a078
  - [bpf-next,v3,3/6] bpf, sockmap: remove skb_set_owner_w wmem will be taken later from sendpage
    https://git.kernel.org/bpf/bpf-next/c/29545f4977cf
  - [bpf-next,v3,4/6] bpf, sockmap: remove dropped data on errors in redirect case
    https://git.kernel.org/bpf/bpf-next/c/9047f19e7ccb
  - [bpf-next,v3,5/6] bpf, sockmap: Remove skb_orphan and let normal skb_kfree do cleanup
    https://git.kernel.org/bpf/bpf-next/c/10d58d006356
  - [bpf-next,v3,6/6] bpf, sockmap: Add memory accounting so skbs on ingress lists are visible
    https://git.kernel.org/bpf/bpf-next/c/0b17ad25d8d1

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