From: Lorenz Brun <lorenz@monogon.tech>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Lorenz Brun <lorenz@monogon.tech>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] net: add config option for tunnel fallback devs
Date: Fri, 13 Sep 2024 13:02:33 +0200 [thread overview]
Message-ID: <20240913110234.166707-1-lorenz@monogon.tech> (raw)
This adds a Kconfig option to set the default behavior regarding tunnel
fallback devices.
For setups where the initial namespace should also not have these, the
only preexisting option is to use a kernel command line option which
needs to be passed to every kernel invocation, which can be inconvenient
in certain setups.
If a kernel is built for a specific environment this knob allows
disabling the compatibility behavior outright, without requiring any
additional actions.
Signed-off-by: Lorenz Brun <lorenz@monogon.tech>
---
net/Kconfig | 33 +++++++++++++++++++++++++++++++++
net/core/sysctl_net_core.c | 2 +-
2 files changed, 34 insertions(+), 1 deletion(-)
diff --git a/net/Kconfig b/net/Kconfig
index d27d0deac0bf..e4429a017e47 100644
--- a/net/Kconfig
+++ b/net/Kconfig
@@ -447,6 +447,39 @@ config LWTUNNEL_BPF
Allows to run BPF programs as a nexthop action following a route
lookup for incoming and outgoing packets.
+choice
+ prompt "Create fallback tunnel devices"
+ default FB_TUNNELS_DEFAULT_ALL
+ help
+ Fallback tunnel devices predate the Netlink API for managing network
+ devices in Linux and get created when the respective tunnel kernel module
+ is loaded. With a modern userspace these are no longer used but for
+ compatibility reasons the default is to keep them around as the kernel
+ cannot know if a given userspace needs them.
+ There is a sysctl (net.core.fb_tunnels_only_for_init_net) for changing
+ this, but it cannot retroactively remove fallback tunnel devices created
+ before it was changed.
+
+ This knob provides the possibility to set this behavior in the kernel,
+ making it work in all cases. Note that changing this value to anything
+ other than the default will break compatibility with old userspace.
+
+ config FB_TUNNELS_DEFAULT_ALL
+ bool "In every namespace"
+
+ config FB_TUNNELS_DEFAULT_INITNS
+ bool "Only in the initial namespace"
+
+ config FB_TUNNELS_DEFAULT_NONE
+ bool "Never"
+endchoice
+
+config FB_TUNNELS_DEFAULT
+ int
+ default 0 if FB_TUNNELS_DEFAULT_ALL
+ default 1 if FB_TUNNELS_DEFAULT_INITNS
+ default 2 if FB_TUNNELS_DEFAULT_NONE
+
config DST_CACHE
bool
default n
diff --git a/net/core/sysctl_net_core.c b/net/core/sysctl_net_core.c
index 86a2476678c4..d9a0b13ceb4a 100644
--- a/net/core/sysctl_net_core.c
+++ b/net/core/sysctl_net_core.c
@@ -37,7 +37,7 @@ static int min_mem_pcpu_rsv = SK_MEMORY_PCPU_RESERVE;
static int net_msg_warn; /* Unused, but still a sysctl */
-int sysctl_fb_tunnels_only_for_init_net __read_mostly = 0;
+int sysctl_fb_tunnels_only_for_init_net __read_mostly = CONFIG_FB_TUNNELS_DEFAULT;
EXPORT_SYMBOL(sysctl_fb_tunnels_only_for_init_net);
/* 0 - Keep current behavior:
--
2.44.1
next reply other threads:[~2024-09-13 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 11:02 Lorenz Brun [this message]
2024-09-14 3:08 ` [PATCH] net: add config option for tunnel fallback devs Jakub Kicinski
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=20240913110234.166707-1-lorenz@monogon.tech \
--to=lorenz@monogon.tech \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).