netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, Eric Leblond <eric@regit.org>,
	Florian Westphal <fw@strlen.de>
Subject: [nft PATCH v2 0/5] Get output under application control
Date: Thu, 28 Sep 2017 17:17:40 +0200	[thread overview]
Message-ID: <20170928151745.28426-1-phil@nwl.cc> (raw)

The following series introduces struct output_ctx field 'output_fp' and
adjusts the whole code base to use that for regular (e.g. 'list'
command) and debug output.

Patches 1-4 contain preparation changes which I extracted for easier
review. Patch 5 is a modified version of what Eric Leblond sent earlier
(hence why I tagged this whole series as v2). I sent him parts of it
earlier, but didn't get a reply. So I'll just hijack his work and make
it a joint one between him and me.

Patches 1-4 are new ones not present in Eric's v1. Patch 5 contains a
changelog.

Note that with this series applied, the testsuite (including monitor
tests) passes (apart from the unrelated ICMPv6 asymmetry).

Phil Sutter (5):
  rule: Use C99-style initializer in cache_init()
  exthdr: Simplify tcp option printing a bit
  erec_print: Pass output FILE pointer to netlink_dump_expr()
  rule: Refactor chain_print_declaration()
  src: get rid of printf

 include/datatype.h      |   5 +-
 include/expression.h    |   2 +-
 include/netlink.h       |  10 +-
 include/nftables.h      |   6 +
 include/parser.h        |   2 +-
 include/rule.h          |   7 +-
 src/cli.c               |   2 +-
 src/ct.c                |  20 ++--
 src/datatype.c          |  60 +++++-----
 src/erec.c              |   2 +-
 src/evaluate.c          |  22 ++--
 src/expression.c        |  74 ++++++------
 src/exthdr.c            |  21 ++--
 src/fib.c               |  23 ++--
 src/hash.c              |  10 +-
 src/main.c              |  51 ++++++++-
 src/meta.c              |  32 +++---
 src/netlink.c           | 131 ++++++++++-----------
 src/netlink_linearize.c |   2 +-
 src/numgen.c            |   7 +-
 src/parser_bison.y      |   3 +-
 src/payload.c           |  10 +-
 src/rt.c                |   2 +-
 src/rule.c              | 297 +++++++++++++++++++++++++-----------------------
 src/statement.c         | 138 +++++++++++-----------
 25 files changed, 510 insertions(+), 429 deletions(-)

-- 
2.13.1


             reply	other threads:[~2017-09-28 15:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 15:17 Phil Sutter [this message]
2017-09-28 15:17 ` [nft PATCH v2 1/5] rule: Use C99-style initializer in cache_init() Phil Sutter
2017-09-29 10:25   ` Pablo Neira Ayuso
2017-09-28 15:17 ` [nft PATCH v2 2/5] exthdr: Simplify tcp option printing a bit Phil Sutter
2017-09-29 10:25   ` Pablo Neira Ayuso
2017-09-28 15:17 ` [nft PATCH v2 3/5] erec_print: Pass output FILE pointer to netlink_dump_expr() Phil Sutter
2017-09-29 10:26   ` Pablo Neira Ayuso
2017-09-28 15:17 ` [nft PATCH v2 4/5] rule: Refactor chain_print_declaration() Phil Sutter
2017-09-29 10:26   ` Pablo Neira Ayuso
2017-09-28 15:17 ` [nft PATCH v2 5/5] src: get rid of printf Phil Sutter
2017-09-29 10:38   ` Pablo Neira Ayuso
2017-09-29 10:57     ` Phil Sutter
2017-09-29 11:19       ` 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=20170928151745.28426-1-phil@nwl.cc \
    --to=phil@nwl.cc \
    --cc=eric@regit.org \
    --cc=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).