From: Martin KaFai Lau <martin.lau@linux.dev>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: pablo@netfilter.org, fw@strlen.de, toke@kernel.org,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
memxor@gmail.com
Subject: Re: [PATCH bpf-next v3 3/3] bpf: Move nf_conn extern declarations to filter.h
Date: Tue, 20 Sep 2022 14:52:05 -0700 [thread overview]
Message-ID: <da5fdb0c-cf24-6356-206e-bdde00f0f8fa@linux.dev> (raw)
In-Reply-To: <2bd2e0283df36d8a4119605878edb1838d144174.1663683114.git.dxu@dxuuu.xyz>
On 9/20/22 7:15 AM, Daniel Xu wrote:
> --- a/include/net/netfilter/nf_conntrack_bpf.h
> +++ b/include/net/netfilter/nf_conntrack_bpf.h
> @@ -12,12 +12,6 @@
> extern int register_nf_conntrack_bpf(void);
> extern void cleanup_nf_conntrack_bpf(void);
>
> -extern struct mutex nf_conn_btf_access_lock;
> -extern int (*nfct_btf_struct_access)(struct bpf_verifier_log *log, const struct btf *btf,
> - const struct btf_type *t, int off, int size,
> - enum bpf_access_type atype, u32 *next_btf_id,
> - enum bpf_type_flag *flag);
> -
I removed the 'include mutex.h' from this header and applied. Thanks.
next prev parent reply other threads:[~2022-09-20 21:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 14:15 [PATCH bpf-next v3 0/3] bpf: Small nf_conn cleanups Daniel Xu
2022-09-20 14:15 ` [PATCH bpf-next v3 1/3] bpf: Remove unused btf_struct_access stub Daniel Xu
2022-09-20 14:15 ` [PATCH bpf-next v3 2/3] bpf: Rename nfct_bsa to nfct_btf_struct_access Daniel Xu
2022-09-20 14:15 ` [PATCH bpf-next v3 3/3] bpf: Move nf_conn extern declarations to filter.h Daniel Xu
2022-09-20 21:52 ` Martin KaFai Lau [this message]
2022-09-20 21:50 ` [PATCH bpf-next v3 0/3] bpf: Small nf_conn cleanups patchwork-bot+netdevbpf
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=da5fdb0c-cf24-6356-206e-bdde00f0f8fa@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dxu@dxuuu.xyz \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=toke@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.