netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Subject: [PATCH nf-next 0/7] netfilter: conntrack: constify protocol trackers, part 1
Date: Sat, 12 Aug 2017 00:57:01 +0200	[thread overview]
Message-ID: <20170811225708.22181-1-fw@strlen.de> (raw)

This is an initial series of patches to mark the l3 and l4 protocol handler
structs as const.

Only reason why we can't constify them now is that l3 and l4 trackers
compute netlink attribute size needed at init time and store result in
the proto struct.

First patch switches the l3 trackers to compile-time computation.

Next patches reduce size by (re)moving various pointers.

Last patch adds const qualifiers in a lot of places.  This patch
has no effect on its own but its needed to avoid compiler warnings
when part 2 of the series will constify the trackers.


             reply	other threads:[~2017-08-11 22:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11 22:57 Florian Westphal [this message]
2017-08-11 22:57 ` [PATCH nf-next 1/7] netfilter: conntrack: compute l3proto nla size at compile time Florian Westphal
2017-08-11 22:57 ` [PATCH nf-next 2/7] netfilter: conntrack: remove protocol name from l3proto struct Florian Westphal
2017-08-11 22:57 ` [PATCH nf-next 3/7] netfilter: conntrack: remove protocol name from l4proto struct Florian Westphal
2017-08-11 22:57 ` [PATCH nf-next 4/7] netfilter: conntrack: reduce size of l4protocol trackers Florian Westphal
2017-08-11 22:57 ` [PATCH nf-next 5/7] netfilter: conntrack: place print_tuple in procfs part Florian Westphal
2017-08-11 22:57 ` [PATCH nf-next 6/7] netfilter: conntrack: print_conntrack only needed if CONFIG_NF_CONNTRACK_PROCFS Florian Westphal
2017-08-11 22:57 ` [PATCH nf-next 7/7] netfilter: conntrack: make protocol tracker pointers const Florian Westphal
2017-08-24 16:52 ` [PATCH nf-next 0/7] netfilter: conntrack: constify protocol trackers, part 1 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=20170811225708.22181-1-fw@strlen.de \
    --to=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 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).