From: Eric Leblond <eric@regit.org>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [nft PATCH 0/3] fix a delinearization issue
Date: Thu, 26 Feb 2015 00:51:07 +0100 [thread overview]
Message-ID: <1424908270-554-1-git-send-email-eric@regit.org> (raw)
Hello,
This small patchset is fixing a ntables delinearization issue when
using counter. The rule triggering this is not straightforward as
it relays on statement order:
ip protocol tcp counter packets tcp dport ssh accept
But it is possible some users are using this kind of rules so it
should be linearized and delinearized correctly.
With current code it was converted when reading rules from kernel
to:
counter packets tcp dport ssh accept
BR,
--
Eric
next reply other threads:[~2015-02-26 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 23:51 Eric Leblond [this message]
2015-02-25 23:51 ` [nft PATCH 1/3] regression: fix typo in README Eric Leblond
2015-02-25 23:51 ` [nft PATCH 2/3] regression: add test on counter related issue Eric Leblond
2015-02-25 23:51 ` [nft PATCH 3/3] netlink_delinearize: fix postprocessing Eric Leblond
2015-02-26 8:40 ` Patrick McHardy
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=1424908270-554-1-git-send-email-eric@regit.org \
--to=eric@regit.org \
--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).