From: Yonghong Song <yhs@fb.com>
To: Mark Pashmfouroush <markpash@cloudflare.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>
Cc: <kernel-team@cloudflare.com>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next v2 1/2] bpf: Add ifindex to bpf_sk_lookup
Date: Thu, 4 Nov 2021 11:06:21 -0700 [thread overview]
Message-ID: <32332bb4-1848-0280-9482-5189ab912b02@fb.com> (raw)
In-Reply-To: <20211104122304.962104-2-markpash@cloudflare.com>
On 11/4/21 5:23 AM, Mark Pashmfouroush wrote:
> It may be helpful to have access to the ifindex during bpf socket
> lookup. An example may be to scope certain socket lookup logic to
> specific interfaces, i.e. an interface may be made exempt from custom
> lookup code.
>
> Add the ifindex of the arriving connection to the bpf_sk_lookup API.
>
> Signed-off-by: Mark Pashmfouroush <markpash@cloudflare.com>
>
> diff --git a/include/linux/filter.h b/include/linux/filter.h
> index 24b7ed2677af..0012a5176a32 100644
> --- a/include/linux/filter.h
> +++ b/include/linux/filter.h
> @@ -1374,6 +1374,7 @@ struct bpf_sk_lookup_kern {
> const struct in6_addr *daddr;
> } v6;
> struct sock *selected_sk;
> + u32 ifindex;
In struct __sk_buff, we have two ifindex related fields:
__u32 ingress_ifindex;
__u32 ifindex;
Does newly-added ifindex corresponds to skb->ingress_ifindex or
skb->ifindex? From comments:
> + __u32 ifindex; /* The arriving interface. Determined by inet_iif. */
looks like it corresponds to ingress? Should be use the name
ingress_ifindex to be consistent with __sk_buff?
> bool no_reuseport;
> };
>
> @@ -1436,7 +1437,7 @@ extern struct static_key_false bpf_sk_lookup_enabled;
> static inline bool bpf_sk_lookup_run_v4(struct net *net, int protocol,
> const __be32 saddr, const __be16 sport,
> const __be32 daddr, const u16 dport,
> - struct sock **psk)
> + const int ifindex, struct sock **psk)
> {
> struct bpf_prog_array *run_array;
> struct sock *selected_sk = NULL;
> @@ -1452,6 +1453,7 @@ static inline bool bpf_sk_lookup_run_v4(struct net *net, int protocol,
> .v4.daddr = daddr,
> .sport = sport,
> .dport = dport,
> + .ifindex = ifindex,
> };
> u32 act;
>
> @@ -1474,7 +1476,7 @@ static inline bool bpf_sk_lookup_run_v6(struct net *net, int protocol,
> const __be16 sport,
> const struct in6_addr *daddr,
> const u16 dport,
> - struct sock **psk)
> + const int ifindex, struct sock **psk)
> {
> struct bpf_prog_array *run_array;
> struct sock *selected_sk = NULL;
> @@ -1490,6 +1492,7 @@ static inline bool bpf_sk_lookup_run_v6(struct net *net, int protocol,
> .v6.daddr = daddr,
> .sport = sport,
> .dport = dport,
> + .ifindex = ifindex,
> };
> u32 act;
>
> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
> index ba5af15e25f5..5b8618a4d485 100644
> --- a/include/uapi/linux/bpf.h
> +++ b/include/uapi/linux/bpf.h
> @@ -6296,6 +6296,7 @@ struct bpf_sk_lookup {
> __u32 local_ip4; /* Network byte order */
> __u32 local_ip6[4]; /* Network byte order */
> __u32 local_port; /* Host byte order */
> + __u32 ifindex; /* The arriving interface. Determined by inet_iif. */
> };
[...]
next prev parent reply other threads:[~2021-11-04 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211104122304.962104-1-markpash@cloudflare.com>
2021-11-04 12:23 ` Mark Pashmfouroush
2021-11-04 18:06 ` Yonghong Song [this message]
2021-11-05 14:47 ` Jakub Sitnicki
2021-11-04 12:23 ` [PATCH bpf-next v2 2/2] selftests/bpf: Add tests for accessing ifindex in bpf_sk_lookup Mark Pashmfouroush
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=32332bb4-1848-0280-9482-5189ab912b02@fb.com \
--to=yhs@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markpash@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/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
all inboxes | Powered by JetHome®