From: John Fastabend <john.fastabend@gmail.com>
To: bpf@vger.kernel.org, netdev@vger.kernel.org
Cc: daniel@iogearbox.net, joamaki@gmail.com,
xiyou.wangcong@gmail.com, jakub@cloudflare.com,
john.fastabend@gmail.com
Subject: [PATCH bpf v2 0/5] bpf, sockmap: fixes stress testing and regression
Date: Wed, 3 Nov 2021 13:47:31 -0700 [thread overview]
Message-ID: <20211103204736.248403-1-john.fastabend@gmail.com> (raw)
Attached are 5 patches that fix issues we found by either stress testing
or updating our CI to LTS kernels.
Thanks to Jussi for all the hard work tracking down issues and getting
stress testing/CI running.
First patch was suggested by Jakub to ensure sockets in CLOSE state
were safe from helper side.
Next two patches are issues discovered by Jussi after writing a stess
testing tool.
The last two fix an issue noticed while reviewing patches and xlated
code paths also discovered by Jussi.
v2: Add an initial patch to make sockmap helpers safe with CLOSE
sockets in sockmap
Added Jussi's tested-by line he tested the original patch series.
John Fastabend (4):
bpf, sockmap: Use stricter sk state checks in sk_lookup_assign
bpf, sockmap: Remove unhash handler for BPF sockmap usage
bpf, sockmap: Fix race in ingress receive verdict with redirect to
self
bpf: sockmap, strparser, and tls are reusing qdisc_skb_cb and
colliding
Jussi Maki (1):
bpf, sockmap: sk_skb data_end access incorrect when src_reg = dst_reg
include/linux/skmsg.h | 12 ++++++++
include/net/strparser.h | 20 +++++++++++-
net/core/filter.c | 64 ++++++++++++++++++++++++++++++++++-----
net/core/sock_map.c | 6 ----
net/ipv4/tcp_bpf.c | 48 ++++++++++++++++++++++++++++-
net/strparser/strparser.c | 10 +-----
6 files changed, 135 insertions(+), 25 deletions(-)
--
2.33.0
next reply other threads:[~2021-11-03 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 20:47 John Fastabend [this message]
2021-11-03 20:47 ` [PATCH bpf v2 1/5] bpf, sockmap: Use stricter sk state checks in sk_lookup_assign John Fastabend
2021-11-08 10:10 ` Jakub Sitnicki
2021-11-03 20:47 ` [PATCH bpf v2 2/5] bpf, sockmap: Remove unhash handler for BPF sockmap usage John Fastabend
2021-11-03 20:47 ` [PATCH bpf v2 3/5] bpf, sockmap: Fix race in ingress receive verdict with redirect to self John Fastabend
2021-11-03 20:47 ` [PATCH bpf v2 4/5] bpf: sockmap, strparser, and tls are reusing qdisc_skb_cb and colliding John Fastabend
2021-11-03 20:47 ` [PATCH bpf v2 5/5] bpf, sockmap: sk_skb data_end access incorrect when src_reg = dst_reg John Fastabend
2021-11-08 10:16 ` [PATCH bpf v2 0/5] bpf, sockmap: fixes stress testing and regression Jakub Sitnicki
2021-11-09 0:10 ` patchwork-bot+netdevbpf
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=20211103204736.248403-1-john.fastabend@gmail.com \
--to=john.fastabend@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub@cloudflare.com \
--cc=joamaki@gmail.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).