From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Fastabend Subject: [bpf PATCH v2 0/3] bpf, sockmap ESTABLISHED state only Date: Mon, 17 Sep 2018 10:59:12 -0700 Message-ID: <20180917175801.3870.61111.stgit@john-Precision-Tower-5810> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: edumazet@google.com, ast@kernel.org, daniel@iogearbox.net Return-path: Received: from [184.63.162.180] ([184.63.162.180]:56822 "EHLO john-Precision-Tower-5810" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1727176AbeIQX1n (ORCPT ); Mon, 17 Sep 2018 19:27:43 -0400 Sender: netdev-owner@vger.kernel.org List-ID: Eric noted that using the close callback is not sufficient to catch all transitions from ESTABLISHED state to a LISTEN state. So this series does two things. First, only allow adding socks in ESTABLISH state and second use unhash callback to catch tcp_disconnect() transitions. v2: Added check for ESTABLISH state in hash update sockmap as well. Thanks, John --- John Fastabend (3): bpf: sockmap only allow ESTABLISHED sock state bpf: sockmap, fix transition through disconnect without close bpf: test_maps, only support ESTABLISHED socks kernel/bpf/sockmap.c | 102 +++++++++++++++++++++++++------ tools/testing/selftests/bpf/test_maps.c | 10 ++- 2 files changed, 89 insertions(+), 23 deletions(-)