[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5f80a621d81e0_d21e20870@john-XPS-13-9370.notmuch>
Date: Fri, 09 Oct 2020 11:04:17 -0700
From: John Fastabend <john.fastabend@...il.com>
To: John Fastabend <john.fastabend@...il.com>,
john.fastabend@...il.com, alexei.starovoitov@...il.com,
daniel@...earbox.net
Cc: netdev@...r.kernel.org, bpf@...r.kernel.org, jakub@...udflare.com,
lmb@...udflare.com
Subject: RE: [bpf-next PATCH v2 0/6] sockmap/sk_skb program memory acct fixes
John Fastabend 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
Will need a v3 to fix a typo, should be ready after fix, rebuild
and retest.
> v1->v2: Fix uninitialized/unused variables (kernel test robot)
>
v2->v3: patch2: err = 0 needs to be err = -EIO to use workqueue
> ---
>
> John Fastabend (6):
> bpf, sockmap: skb verdict SK_PASS to self already checked rmem limits
> bpf, sockmap: On receive programs try to fast track SK_PASS ingress
> bpf, sockmap: remove skb_set_owner_w wmem will be taken later from sendpage
> bpf, sockmap: remove dropped data on errors in redirect case
> bpf, sockmap: Remove skb_orphan and let normal skb_kfree do cleanup
> bpf, sockmap: Add memory accounting so skbs on ingress lists are visible
>
>
> net/core/skmsg.c | 83 +++++++++++++++++++++++++++++-------------------------
> 1 file changed, 45 insertions(+), 38 deletions(-)
>
> --
> Signature
Powered by blists - more mailing lists