netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf] netfilter: nft_ct: fix expiration getter
Date: Fri, 8 Jul 2016 16:54:00 +0200	[thread overview]
Message-ID: <20160708145400.GB20973@breakpoint.cc> (raw)
In-Reply-To: <20160708132543.GA23868@salvia>

Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> On Fri, Jul 08, 2016 at 02:56:46PM +0200, Pablo Neira Ayuso wrote:
> > On Wed, Jul 06, 2016 at 02:53:06PM +0200, Florian Westphal wrote:
> > > We need to compute timeout.expires - jiffies, not the other way around.
> > > Add a helper, another patch can then later change more places in
> > > conntrack code where we currently open-code this.
> > >
> > > Will allow us to only change one place later when we remove per-ct timer.
> > 
> > Applied, thanks.
> 
> I just realized that this is broken from userspace, look:
> 
> # nft --debug=netlink add rule x y ct expiration 10s
> ip x y
>   [ ct load expiration => reg 1 ]
>   [ cmp eq reg 1 0x0000000a ]
> 
> <cmdline>:1:1-30: Error: Could not process rule: No such file or
> directory
> add rule x y ct expiration 10s
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> jiffies_to_msecs() returns milliseconds, but userspace uses seconds.

Ack, thanks for catching this.
I only tested that 'ct expiration gt 0' was matching :-/

      reply	other threads:[~2016-07-08 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06 12:53 [PATCH nf] netfilter: nft_ct: fix expiration getter Florian Westphal
2016-07-08 12:56 ` Pablo Neira Ayuso
2016-07-08 13:25   ` Pablo Neira Ayuso
2016-07-08 14:54     ` Florian Westphal [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=20160708145400.GB20973@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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).