All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Maciej Soltysiak <solt@dns.toxicfilms.tv>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ip_conntrack_max registered twice
Date: Wed, 15 Dec 2004 21:59:59 +0100	[thread overview]
Message-ID: <41C0A5CF.4030303@eurodev.net> (raw)
In-Reply-To: <000701c4e2e8$280ae830$0e25fe0a@pysiak>

Maciej Soltysiak wrote:

> Hi,
>
> I noticed that I have:
> /proc/sys/net/ipv4/netfilter/ip_conntrack_max
> /proc/sys/net/ipv4/ip_conntrack_max
>
> A quick look at net/ipv4/netfilter/ip_conntrack_standalone.c shows
> that we register the same variable (ip_conntrack_max) twice:
>
> In:
> ip_ct_sysctl_table[]:
>        {
>                .ctl_name       = NET_IPV4_NF_CONNTRACK_MAX,
>                .procname       = "ip_conntrack_max",
>                .data           = &ip_conntrack_max,
>                .maxlen         = sizeof(int),
>                .mode           = 0644,
>                .proc_handler   = &proc_dointvec,
>        },
>
> And in ip_ct_netfilter_table[]:
>        {
>                .ctl_name       = NET_IP_CONNTRACK_MAX,
>                .procname       = "ip_conntrack_max",
>                .data           = &ip_conntrack_max,
>                .maxlen         = sizeof(int),
>                .mode           = 0644,
>                .proc_handler   = &proc_dointvec
>        },
>
> Is this for some backward compatibility or is it a needless duplication ?


I asked the same some time ago, and Jozsef told me that it's a backward 
compatibility issue.

--
Pablo

  reply	other threads:[~2004-12-15 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 20:53 ip_conntrack_max registered twice Maciej Soltysiak
2004-12-15 20:59 ` Pablo Neira [this message]
2004-12-16  9:24   ` Maciej Soltysiak

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=41C0A5CF.4030303@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=solt@dns.toxicfilms.tv \
    /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.