public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stanislav Fomichev <sdf@google•com>
To: netdev@vger•kernel.org, linux-kselftest@vger•kernel.org,
	ast@kernel•org, daniel@iogearbox•net, shuah@kernel•org
Cc: jakub.kicinski@netronome•com, quentin.monnet@netronome•com,
	guro@fb•com, jiong.wang@netronome•com, sdf@google•com,
	bhole_prashant_q7@lab•ntt.co.jp, john.fastabend@gmail•com,
	jbenc@redhat•com, treeze.taeung@gmail•com, yhs@fb•com,
	osk@fb•com, sandipan@linux•vnet.ibm.com
Subject: [PATCH bpf-next 1/2] selftests/bpf: rename flow dissector section to flow_dissector
Date: Wed,  7 Nov 2018 11:35:51 -0800	[thread overview]
Message-ID: <20181107193552.77894-2-sdf@google.com> (raw)
In-Reply-To: <20181107193552.77894-1-sdf@google.com>

Makes it compatible with the logic that derives program type
from section name in libbpf_prog_type_by_name.

Signed-off-by: Stanislav Fomichev <sdf@google•com>
---
 tools/testing/selftests/bpf/bpf_flow.c             | 2 +-
 tools/testing/selftests/bpf/test_flow_dissector.sh | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/bpf/bpf_flow.c b/tools/testing/selftests/bpf/bpf_flow.c
index 107350a7821d..b9798f558ca7 100644
--- a/tools/testing/selftests/bpf/bpf_flow.c
+++ b/tools/testing/selftests/bpf/bpf_flow.c
@@ -116,7 +116,7 @@ static __always_inline int parse_eth_proto(struct __sk_buff *skb, __be16 proto)
 	return BPF_DROP;
 }
 
-SEC("dissect")
+SEC("flow_dissector")
 int _dissect(struct __sk_buff *skb)
 {
 	if (!skb->vlan_present)
diff --git a/tools/testing/selftests/bpf/test_flow_dissector.sh b/tools/testing/selftests/bpf/test_flow_dissector.sh
index c0fb073b5eab..d23d4da66b83 100755
--- a/tools/testing/selftests/bpf/test_flow_dissector.sh
+++ b/tools/testing/selftests/bpf/test_flow_dissector.sh
@@ -59,7 +59,7 @@ else
 fi
 
 # Attach BPF program
-./flow_dissector_load -p bpf_flow.o -s dissect
+./flow_dissector_load -p bpf_flow.o -s flow_dissector
 
 # Setup
 tc qdisc add dev lo ingress
-- 
2.19.1.930.g4563a0d9d0-goog

  reply	other threads:[~2018-11-08  5:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 19:35 [PATCH bpf-next 0/2] bpftool: support loading flow dissector Stanislav Fomichev
2018-11-07 19:35 ` Stanislav Fomichev [this message]
2018-11-07 19:35 ` [PATCH bpf-next 2/2] " Stanislav Fomichev
2018-11-07 20:03   ` Jakub Kicinski
2018-11-07 21:00     ` Stanislav Fomichev
2018-11-07 21:12       ` Jakub Kicinski
2018-11-07 20:08   ` Quentin Monnet
2018-11-07 20:32     ` Jakub Kicinski
2018-11-07 21:34       ` Quentin Monnet
2018-11-07 22:15         ` Stanislav Fomichev
2018-11-07 22:51           ` Jakub Kicinski
2018-11-07 23:12             ` Stanislav Fomichev
2018-11-07 23:30               ` Jakub Kicinski
2018-11-07 21:17     ` Stanislav Fomichev

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=20181107193552.77894-2-sdf@google.com \
    --to=sdf@google$(echo .)com \
    --cc=ast@kernel$(echo .)org \
    --cc=bhole_prashant_q7@lab$(echo .)ntt.co.jp \
    --cc=daniel@iogearbox$(echo .)net \
    --cc=guro@fb$(echo .)com \
    --cc=jakub.kicinski@netronome$(echo .)com \
    --cc=jbenc@redhat$(echo .)com \
    --cc=jiong.wang@netronome$(echo .)com \
    --cc=john.fastabend@gmail$(echo .)com \
    --cc=linux-kselftest@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=osk@fb$(echo .)com \
    --cc=quentin.monnet@netronome$(echo .)com \
    --cc=sandipan@linux$(echo .)vnet.ibm.com \
    --cc=shuah@kernel$(echo .)org \
    --cc=treeze.taeung@gmail$(echo .)com \
    --cc=yhs@fb$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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