From: Phil Sutter <phil@nwl.cc>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next] netfilter: conntrack: avoid same-timeout update
Date: Thu, 21 Feb 2019 16:08:50 +0100 [thread overview]
Message-ID: <20190221150850.GS23745@orbyte.nwl.cc> (raw)
In-Reply-To: <20190221143829.7252-1-fw@strlen.de>
On Thu, Feb 21, 2019 at 03:38:29PM +0100, Florian Westphal wrote:
> No need to dirty a cache line if timeout is unchanged.
> Also, WARN() is useless here: we crash on 'skb->len' access
> if skb is NULL.
>
> Last, ct->timeout is u32, not 'unsigned long' so adapt the
> function prototype accordingly.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
> include/net/netfilter/nf_conntrack.h | 10 +++++-----
> net/netfilter/nf_conntrack_core.c | 9 ++++-----
> 2 files changed, 9 insertions(+), 10 deletions(-)
>
> diff --git a/include/net/netfilter/nf_conntrack.h b/include/net/netfilter/nf_conntrack.h
> index b5aac5ae5129..2270ee5202e3 100644
> --- a/include/net/netfilter/nf_conntrack.h
> +++ b/include/net/netfilter/nf_conntrack.h
> @@ -190,23 +190,23 @@ bool nf_ct_get_tuplepr(const struct sk_buff *skb, unsigned int nhoff,
>
> void __nf_ct_refresh_acct(struct nf_conn *ct, enum ip_conntrack_info ctinfo,
> const struct sk_buff *skb,
> - unsigned long extra_jiffies, int do_acct);
> + u32, bool do_acct);
Maybe not worth a respin, but this mix of named and unnamed parameters
in function prototype is probably not intentional.
Cheers, Phil
next prev parent reply other threads:[~2019-02-21 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 14:38 [PATCH nf-next] netfilter: conntrack: avoid same-timeout update Florian Westphal
2019-02-21 15:08 ` Phil Sutter [this message]
2019-02-21 15:12 ` Florian Westphal
2019-02-27 9:59 ` 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=20190221150850.GS23745@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=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 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.