From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nf-next v2 0/3] netfilter: conntrack sparse annotations
Date: Wed, 22 Jun 2022 11:00:44 +0200 [thread overview]
Message-ID: <20220622090047.24586-1-fw@strlen.de> (raw)
This series reduces the number of generated sparse warnings
in the netfilter codebase.
In some cases its just due to a missing '__rcu' annotation
of the base pointer, but in some other cases there is a
direct access to a __rcu annotated base pointer.
v2: keep unrelated EXPORT_SYMBOL in patch 3.
Florian Westphal (3):
netfilter: nf_conntrack: add missing __rcu annotations
netfilter: nf_conntrack: use rcu accessors where needed
netfilter: h323: merge nat hook pointers into one
include/linux/netfilter/nf_conntrack_h323.h | 109 ++++----
include/linux/netfilter/nf_conntrack_sip.h | 2 +-
include/net/netfilter/nf_conntrack_timeout.h | 2 +-
net/ipv4/netfilter/nf_nat_h323.c | 42 +--
net/netfilter/nf_conntrack_broadcast.c | 6 +-
net/netfilter/nf_conntrack_h323_main.c | 259 +++++++------------
net/netfilter/nf_conntrack_helper.c | 2 +-
net/netfilter/nf_conntrack_netlink.c | 9 +-
net/netfilter/nf_conntrack_pptp.c | 2 +-
net/netfilter/nf_conntrack_sip.c | 9 +-
net/netfilter/nf_conntrack_timeout.c | 18 +-
net/netfilter/nfnetlink_cthelper.c | 10 +-
net/netfilter/xt_CT.c | 23 +-
13 files changed, 230 insertions(+), 263 deletions(-)
--
2.35.1
next reply other threads:[~2022-06-22 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 9:00 Florian Westphal [this message]
2022-06-22 9:00 ` [PATCH nf-next v2 1/3] netfilter: nf_conntrack: add missing __rcu annotations Florian Westphal
2022-06-22 9:00 ` [PATCH nf-next v2 2/3] netfilter: nf_conntrack: use rcu accessors where needed Florian Westphal
2022-06-22 9:00 ` [PATCH nf-next v2 3/3] netfilter: h323: merge nat hook pointers into one Florian Westphal
2022-07-11 14:38 ` [PATCH nf-next v2 0/3] netfilter: conntrack sparse annotations Pablo Neira Ayuso
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=20220622090047.24586-1-fw@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).