From: Roi Dayan <roid@nvidia.com>
To: Florian Westphal <fw@strlen.de>, netdev@vger.kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
netfilter-devel@vger.kernel.org, Maor Dickman <maord@nvidia.com>
Subject: Re: [PATCH net-next 3/9] netfilter: conntrack: avoid reload of ct->status
Date: Mon, 23 Jan 2023 13:38:03 +0200 [thread overview]
Message-ID: <b352f87d-fe0d-a5ff-451c-57376f6f3bc3@nvidia.com> (raw)
In-Reply-To: <20230118123208.17167-4-fw@strlen.de>
On 18/01/2023 14:32, Florian Westphal wrote:
> Compiler can't merge the two test_bit() calls, so load ct->status
> once and use non-atomic accesses.
>
> This is fine because IPS_EXPECTED or NAT_CLASH are either set at ct
> creation time or not at all, but compiler can't know that.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
> net/netfilter/nf_conntrack_core.c | 9 +++++----
> net/netfilter/nf_conntrack_proto_udp.c | 10 ++++++----
> 2 files changed, 11 insertions(+), 8 deletions(-)
>
> diff --git a/net/netfilter/nf_conntrack_core.c b/net/netfilter/nf_conntrack_core.c
> index 81ece117033a..9e12cade4e0f 100644
> --- a/net/netfilter/nf_conntrack_core.c
> +++ b/net/netfilter/nf_conntrack_core.c
> @@ -1854,14 +1854,15 @@ resolve_normal_ct(struct nf_conn *tmpl,
> if (NF_CT_DIRECTION(h) == IP_CT_DIR_REPLY) {
> ctinfo = IP_CT_ESTABLISHED_REPLY;
> } else {
> + unsigned long status = READ_ONCE(ct->status);
> +
> /* Once we've had two way comms, always ESTABLISHED. */
> - if (test_bit(IPS_SEEN_REPLY_BIT, &ct->status)) {
> + if (likely(status & IPS_SEEN_REPLY))
> ctinfo = IP_CT_ESTABLISHED;
> - } else if (test_bit(IPS_EXPECTED_BIT, &ct->status)) {
> + else if (status & IPS_EXPECTED)
> ctinfo = IP_CT_RELATED;
> - } else {
> + else
> ctinfo = IP_CT_NEW;
> - }
> }
> nf_ct_set(skb, ct, ctinfo);
> return 0;
> diff --git a/net/netfilter/nf_conntrack_proto_udp.c b/net/netfilter/nf_conntrack_proto_udp.c
> index 3b516cffc779..6b9206635b24 100644
> --- a/net/netfilter/nf_conntrack_proto_udp.c
> +++ b/net/netfilter/nf_conntrack_proto_udp.c
> @@ -88,6 +88,7 @@ int nf_conntrack_udp_packet(struct nf_conn *ct,
> const struct nf_hook_state *state)
> {
> unsigned int *timeouts;
> + unsigned long status;
>
> if (udp_error(skb, dataoff, state))
> return -NF_ACCEPT;
> @@ -96,26 +97,27 @@ int nf_conntrack_udp_packet(struct nf_conn *ct,
> if (!timeouts)
> timeouts = udp_get_timeouts(nf_ct_net(ct));
>
> - if (!nf_ct_is_confirmed(ct))
> + status = READ_ONCE(ct->status);
> + if ((status & IPS_CONFIRMED) == 0)
> ct->proto.udp.stream_ts = 2 * HZ + jiffies;
>
> /* If we've seen traffic both ways, this is some kind of UDP
> * stream. Set Assured.
> */
> - if (test_bit(IPS_SEEN_REPLY_BIT, &ct->status)) {
> + if (status & IPS_SEEN_REPLY_BIT) {
Hi,
This change has a bug not matching reply status anymore.
Since you don't use test_bit() you should use IPS_SEEN_REPLY
instead of IPS_SEEN_REPLY_BIT.
Thanks,
Roi
> unsigned long extra = timeouts[UDP_CT_UNREPLIED];
> bool stream = false;
>
> /* Still active after two seconds? Extend timeout. */
> if (time_after(jiffies, ct->proto.udp.stream_ts)) {
> extra = timeouts[UDP_CT_REPLIED];
> - stream = true;
> + stream = (status & IPS_ASSURED) == 0;
> }
>
> nf_ct_refresh_acct(ct, ctinfo, skb, extra);
>
> /* never set ASSURED for IPS_NAT_CLASH, they time out soon */
> - if (unlikely((ct->status & IPS_NAT_CLASH)))
> + if (unlikely((status & IPS_NAT_CLASH)))
> return NF_ACCEPT;
>
> /* Also, more likely to be important, and not a probe */
next prev parent reply other threads:[~2023-01-23 11:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 12:31 [PATCH net-next 0/9] Netfilter updates for net-next Florian Westphal
2023-01-18 12:32 ` [PATCH net-next 1/9] netfilter: conntrack: sctp: use nf log infrastructure for invalid packets Florian Westphal
2023-01-18 13:30 ` patchwork-bot+netdevbpf
2023-01-18 12:32 ` [PATCH net-next 2/9] netfilter: conntrack: remove pr_debug calls Florian Westphal
2023-01-18 12:32 ` [PATCH net-next 3/9] netfilter: conntrack: avoid reload of ct->status Florian Westphal
2023-01-23 11:38 ` Roi Dayan [this message]
2023-01-18 12:32 ` [PATCH net-next 4/9] netfilter: conntrack: move rcu read lock to nf_conntrack_find_get Florian Westphal
2023-01-18 12:32 ` [PATCH net-next 5/9] netfilter: ip_tables: remove clusterip target Florian Westphal
2023-01-18 12:32 ` [PATCH net-next 6/9] netfilter: nf_tables: add static key to skip retpoline workarounds Florian Westphal
2023-01-18 12:32 ` [PATCH net-next 7/9] netfilter: nf_tables: avoid retpoline overhead for objref calls Florian Westphal
2023-01-18 12:32 ` [PATCH net-next 8/9] netfilter: nf_tables: avoid retpoline overhead for some ct expression calls Florian Westphal
2023-01-18 12:32 ` [PATCH net-next 9/9] netfilter: nf_tables: add support to destroy operation Florian Westphal
2023-01-19 7:29 ` Vlad Buslov
2023-01-20 9:58 ` Fernando F. Mancera
2023-01-20 10:06 ` Fernando F. Mancera
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=b352f87d-fe0d-a5ff-451c-57376f6f3bc3@nvidia.com \
--to=roid@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=maord@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).