From: patchwork-bot+netdevbpf@kernel.org
To: John Fastabend <john.fastabend@gmail.com>
Cc: xiyou.wangcong@gmail.com, andrii.nakryiko@gmail.com,
daniel@iogearbox.net, ast@fb.com, bpf@vger.kernel.org,
netdev@vger.kernel.org, lmb@cloudflare.com
Subject: Re: [PATCH bpf v2 0/2] bpf, sockmap fixes
Date: Tue, 06 Apr 2021 23:40:09 +0000 [thread overview]
Message-ID: <161775240908.19905.12958340313849612276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <161731427139.68884.1934993103507544474.stgit@john-XPS-13-9370>
Hello:
This series was applied to bpf/bpf.git (refs/heads/master):
On Thu, 01 Apr 2021 14:59:58 -0700 you wrote:
> This addresses an issue found while reviewing latest round of sock
> map patches and an issue reported from CI via Andrii. After this
> CI ./test_maps is stable for me.
>
> The CI discovered issue was introduced by over correcting our
> previously broken memory accounting. After the fix, "bpf, sockmap:
> Avoid returning unneeded EAGAIN when redirecting to self" we fixed
> a dropped packet and a missing fwd_alloc calculations, but pushed
> it too far back into the packet pipeline creating an issue in the
> unlikely case socket tear down happens with an enqueued skb. See
> patch for details.
>
> [...]
Here is the summary with links:
- [bpf,v2,1/2] bpf, sockmap: fix sk->prot unhash op reset
https://git.kernel.org/bpf/bpf/c/1c84b33101c8
- [bpf,v2,2/2] bpf, sockmap: fix incorrect fwd_alloc accounting
https://git.kernel.org/bpf/bpf/c/144748eb0c44
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-04-06 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 21:59 [PATCH bpf v2 0/2] bpf, sockmap fixes John Fastabend
2021-04-01 22:00 ` [PATCH bpf v2 1/2] bpf, sockmap: fix sk->prot unhash op reset John Fastabend
2021-04-01 22:00 ` [PATCH bpf v2 2/2] bpf, sockmap: fix incorrect fwd_alloc accounting John Fastabend
2021-04-06 23:40 ` patchwork-bot+netdevbpf [this message]
2021-05-05 18:26 ` [PATCH bpf v2 0/2] bpf, sockmap fixes Andrii Nakryiko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161775240908.19905.12958340313849612276.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=lmb@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).