All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v8 0/5] add skc_to_mptcp_sock
Date: Tue,  8 Mar 2022 18:47:27 +0800	[thread overview]
Message-ID: <cover.1646736285.git.geliang.tang@suse.com> (raw)

v8:
 - update as Matt suggested.

v7:
 - parse msk token from the output of 'ip mptcp monitor'.
 - add Nicolas and Matt's SoB tags.

v6:
 - add skc_to_mptcp_sock helper and test

RESEND:
 - fix the CI Build Failure.
v5:
 - fix incorrect token value
 - verify the token in selftest

v4:
 - define bpf_mptcp_sock_proto as a static function, no longer export
   it in linux/bpf.h

v3:
 - use RET_PTR_TO_BTF_ID_OR_NULL instead of RET_PTR_TO_MPTCP_SOCK_OR_NULL
 - add a new bpf_id BTF_SOCK_TYPE_MPTCP

v2:
 - keep RET_PTR_TO_MPTCP_SOCK_OR_NULL. If we use RET_PTR_TO_BTF_ID_OR_NULL
instead of RET_PTR_TO_MPTCP_SOCK_OR_NULL as Alexei suggested, the
"userspace" tests developed by Nicolas will break.

Geliang Tang (5):
  Revert "selftests: bpf: add bpf_mptcp_sock() verifier tests"
  Revert "bpf: add 'bpf_mptcp_sock' structure and helper"
  bpf: add skc_to_mptcp_sock helper
  Squash to "selftests: bpf: add MPTCP test base"
  selftests: bpf: add skc_to_mptcp_sock test

 include/linux/bpf.h                           |  31 +----
 include/linux/btf_ids.h                       |   3 +-
 include/uapi/linux/bpf.h                      |  14 +--
 kernel/bpf/verifier.c                         |  20 ----
 net/core/filter.c                             |  21 +++-
 net/mptcp/bpf.c                               |  62 +---------
 scripts/bpf_doc.py                            |   4 +-
 tools/include/uapi/linux/bpf.h                |  14 +--
 tools/testing/selftests/bpf/bpf_tcp_helpers.h |   6 +
 .../testing/selftests/bpf/prog_tests/mptcp.c  | 108 +++++++++++++++---
 tools/testing/selftests/bpf/progs/mptcp.c     |  22 ++++
 tools/testing/selftests/bpf/verifier/sock.c   |  63 ----------
 12 files changed, 157 insertions(+), 211 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-03-08 10:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 10:47 Geliang Tang [this message]
2022-03-08 10:47 ` [PATCH mptcp-next v8 1/5] Revert "selftests: bpf: add bpf_mptcp_sock() verifier tests" Geliang Tang
2022-03-08 10:47 ` [PATCH mptcp-next v8 2/5] Revert "bpf: add 'bpf_mptcp_sock' structure and helper" Geliang Tang
2022-03-08 10:47 ` [PATCH mptcp-next v8 3/5] bpf: add skc_to_mptcp_sock helper Geliang Tang
2022-03-08 10:47 ` [PATCH mptcp-next v8 4/5] Squash to "selftests: bpf: add MPTCP test base" Geliang Tang
2022-03-08 10:47 ` [PATCH mptcp-next v8 5/5] selftests: bpf: add skc_to_mptcp_sock test Geliang Tang
2022-03-08 11:56   ` selftests: bpf: add skc_to_mptcp_sock test: Tests Results MPTCP CI

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=cover.1646736285.git.geliang.tang@suse.com \
    --to=geliang.tang@suse.com \
    --cc=mptcp@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.