[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191011082946.22695-1-jakub@cloudflare.com>
Date: Fri, 11 Oct 2019 10:29:44 +0200
From: Jakub Sitnicki <jakub@...udflare.com>
To: bpf@...r.kernel.org
Cc: netdev@...r.kernel.org, kernel-team@...udflare.com
Subject: [PATCH bpf-next v3 0/2] Atomic flow dissector updates
This patch set changes how bpf(BPF_PROG_ATTACH) operates on flow dissector
hook when there is already a program attached. After this change the user
is allowed to update the program in a single syscall. Please see the first
patch for rationale.
v1 -> v2:
- Don't use CHECK macro which expects BPF program run duration, which we
don't track in attach/detach tests. Suggested by Stanislav Fomichev.
- Test re-attaching flow dissector in both root and non-root network
namespace. Suggested by Stanislav Fomichev.
v2 -> v3:
- Rebased onto recent bpf-next 63098555cfe0 ("Merge branch
'bpf-romap-known-scalars'").
Jakub Sitnicki (2):
flow_dissector: Allow updating the flow dissector program atomically
selftests/bpf: Check that flow dissector can be re-attached
net/core/flow_dissector.c | 10 +-
.../bpf/prog_tests/flow_dissector_reattach.c | 127 ++++++++++++++++++
2 files changed, 134 insertions(+), 3 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/flow_dissector_reattach.c
--
2.20.1
Powered by blists - more mailing lists