From: Daniel Borkmann <daniel@iogearbox.net>
To: Ben Dooks <ben.dooks@codethink.co.uk>, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
sdf@google.com
Subject: Re: [PATCH] bpf: declare bpf_sk_storage_get_cg_sock_proto
Date: Mon, 27 Nov 2023 15:20:32 +0100 [thread overview]
Message-ID: <c9628533-52c8-b497-23ec-e373768a6243@iogearbox.net> (raw)
In-Reply-To: <20231122081317.145355-1-ben.dooks@codethink.co.uk>
On 11/22/23 9:13 AM, Ben Dooks wrote:
> The bpf_sk_storage_get_cg_sock_proto struct is exported from
> net/core/bpf_sk_storage.c but is not decalred in any header
nit: typo
> file. Fix the following sparse warning by adding it to the
> include/net/bpf_sk_storage.h header:
>
> net/core/bpf_sk_storage.c:334:29: warning: symbol 'bpf_sk_storage_get_cg_sock_proto' was not declared. Should it be static
Please add Fixes tag and Cc author (sdf@google.com) as well as bpf@vger.kernel.org:
Fixes: f7c6cb1d9728 ("bpf: Expose socket storage to BPF_PROG_TYPE_CGROUP_SOCK")
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> ---
> include/net/bpf_sk_storage.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/net/bpf_sk_storage.h b/include/net/bpf_sk_storage.h
> index 2926f1f00d65..043155810822 100644
> --- a/include/net/bpf_sk_storage.h
> +++ b/include/net/bpf_sk_storage.h
> @@ -22,6 +22,7 @@ extern const struct bpf_func_proto bpf_sk_storage_get_proto;
> extern const struct bpf_func_proto bpf_sk_storage_delete_proto;
> extern const struct bpf_func_proto bpf_sk_storage_get_tracing_proto;
> extern const struct bpf_func_proto bpf_sk_storage_delete_tracing_proto;
> +extern const struct bpf_func_proto bpf_sk_storage_get_cg_sock_proto;
>
> struct bpf_local_storage_elem;
> struct bpf_sk_storage_diag;
>
prev parent reply other threads:[~2023-11-27 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 8:13 Ben Dooks
2023-11-27 14:20 ` Daniel Borkmann [this message]
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=c9628533-52c8-b497-23ec-e373768a6243@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ben.dooks@codethink.co.uk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
/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®