From: Florian Westphal <fw@strlen.de>
To: avimalin@gmail.com
Cc: vimal.agrawal@sophos.com, linux-kernel@vger.kernel.org,
pablo@netfilter.org, netfilter-devel@vger.kernel.org,
fw@strlen.de, anirudh.gupta@sophos.com
Subject: Re: [PATCH v1] nf_conntrack: sysctl: expose gc worker scan interval via sysctl
Date: Tue, 29 Apr 2025 15:29:21 +0200 [thread overview]
Message-ID: <20250429132921.GA4721@breakpoint.cc> (raw)
In-Reply-To: <20250429130940.74538-1-vimal.agrawal@sophos.com>
avimalin@gmail.com <avimalin@gmail.com> wrote:
> diff --git a/net/netfilter/nf_conntrack_standalone.c b/net/netfilter/nf_conntrack_standalone.c
> index 2f666751c7e7..480ff9a6f185 100644
> --- a/net/netfilter/nf_conntrack_standalone.c
> +++ b/net/netfilter/nf_conntrack_standalone.c
> @@ -559,6 +559,7 @@ enum nf_ct_sysctl_index {
> #ifdef CONFIG_NF_CONNTRACK_TIMESTAMP
> NF_SYSCTL_CT_TIMESTAMP,
> #endif
> + NF_SYSCTL_CT_GC_SCAN_INTERVAL_INIT,
> NF_SYSCTL_CT_PROTO_TIMEOUT_GENERIC,
> NF_SYSCTL_CT_PROTO_TIMEOUT_TCP_SYN_SENT,
> NF_SYSCTL_CT_PROTO_TIMEOUT_TCP_SYN_RECV,
> @@ -691,6 +692,13 @@ static struct ctl_table nf_ct_sysctl_table[] = {
> .extra2 = SYSCTL_ONE,
> },
> #endif
> + [NF_SYSCTL_CT_GC_SCAN_INTERVAL_INIT] = {
> + .procname = "nf_conntrack_gc_scan_interval_init",
> + .data = &nf_conntrack_gc_scan_interval_init,
> + .maxlen = sizeof(unsigned int),
> + .mode = 0644,
> + .proc_handler = proc_dointvec_jiffies,
> + },
> [NF_SYSCTL_CT_PROTO_TIMEOUT_GENERIC] = {
> .procname = "nf_conntrack_generic_timeout",
> .maxlen = sizeof(unsigned int),
I think you'll need to add NF_SYSCTL_CT_GC_SCAN_INTERVAL_INIT to
the
/* Don't allow non-init_net ns to alter global sysctls */
if (!net_eq(&init_net, net)) {
branch in nf_conntrack_standalone_init_sysctl().
next prev parent reply other threads:[~2025-04-29 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 13:09 [PATCH v1] nf_conntrack: sysctl: expose gc worker scan interval via sysctl avimalin
2025-04-29 13:29 ` Florian Westphal [this message]
2025-04-30 6:43 ` [PATCH v2] " avimalin
2025-04-30 7:11 ` Florian Westphal
2025-04-30 7:28 ` [PATCH v3] " avimalin
2025-04-30 7:57 ` Florian Westphal
2025-05-03 2:27 ` Vimal Agrawal
2025-05-08 5:54 ` Vimal Agrawal
2025-10-15 13:32 ` Florian Westphal
2025-11-17 13:23 ` Vimal Agrawal
2025-11-17 14:16 ` Florian Westphal
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=20250429132921.GA4721@breakpoint.cc \
--to=fw@strlen.de \
--cc=anirudh.gupta@sophos.com \
--cc=avimalin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=vimal.agrawal@sophos.com \
/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