OpenVZ Forum


Home » Mailing lists » Devel » [PATCH 1/2] cleanup pernet operation without CONFIG_NET_NS
[PATCH 1/2] cleanup pernet operation without CONFIG_NET_NS [message #22907] Wed, 07 November 2007 11:57 Go to next message
den is currently offline  den
Messages: 494
Registered: December 2005
Senior Member
If CONFIG_NET_NS is not set, the only namespace is possible.

This patch removes list of pernet_operations and cleanups code a bit.
This list is not needed if there are no namespaces. We should just call
->init method.

Additionally, the ->exit will be called on module unloading only. This
case is safe - the code is not discarded. For the in/kernel code, ->exit
should never be called.

Signed-off-by: Denis V. Lunev <den@openvz.org>

--- ./net/core/net_namespace.c.netinitdata	2007-10-15 13:55:25.000000000 +0400
+++ ./net/core/net_namespace.c	2007-11-06 14:33:14.000000000 +0300
@@ -179,6 +180,7 @@ static int __init net_ns_init(void)
 
 pure_initcall(net_ns_init);
 
+#ifdef CONFIG_NET_NS
 static int register_pernet_operations(struct list_head *list,
 				      struct pernet_operations *ops)
 {
@@ -220,6 +222,23 @@ static void unregister_pernet_operations
 			ops->exit(net);
 }
 
+#else
+
+static int register_pernet_operations(struct list_head *list,
+				      struct pernet_operations *ops)
+{
+	if (ops->init == NULL)
+		return 0;
+	return ops->init(&init_net);
+}
+
+static void unregister_pernet_operations(struct pernet_operations *ops)
+{
+	if (ops->exit)
+		ops->exit(&init_net);
+}
+#endif
+
 /**
  *      register_pernet_subsys - register a network namespace subsystem
  *	@ops:  pernet operations structure for the subsystem
Re: [PATCH 1/2] cleanup pernet operation without CONFIG_NET_NS [message #23135 is a reply to message #22907] Tue, 13 November 2007 11:24 Go to previous messageGo to next message
davem is currently offline  davem
Messages: 463
Registered: February 2006
Senior Member
From: "Denis V. Lunev" <den@openvz.org>
Date: Wed, 7 Nov 2007 15:00:07 +0300

> If CONFIG_NET_NS is not set, the only namespace is possible.
> 
> This patch removes list of pernet_operations and cleanups code a bit.
> This list is not needed if there are no namespaces. We should just call
> ->init method.
> 
> Additionally, the ->exit will be called on module unloading only. This
> case is safe - the code is not discarded. For the in/kernel code, ->exit
> should never be called.
> 
> Signed-off-by: Denis V. Lunev <den@openvz.org>

Applied.
Re: [PATCH 1/2] cleanup pernet operation without CONFIG_NET_NS [message #23328 is a reply to message #22907] Thu, 15 November 2007 14:13 Go to previous message
ebiederm is currently offline  ebiederm
Messages: 1354
Registered: February 2006
Senior Member
"Denis V. Lunev" <den@openvz.org> writes:

> If CONFIG_NET_NS is not set, the only namespace is possible.
>
> This patch removes list of pernet_operations and cleanups code a bit.
> This list is not needed if there are no namespaces. We should just call
> ->init method.
>
> Additionally, the ->exit will be called on module unloading only. This
> case is safe - the code is not discarded. For the in/kernel code, ->exit
> should never be called.

This patch looks sane, and reasonable in the !CONFIG_NET_NS case.

Eric
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
Previous Topic: [patch 10/10][NETNS][IP6_FIB] make gc timer handle several network namespace
Next Topic: [PATCH] proc: remove MODULE_LICENSE
Goto Forum:
  


Current Time: Sun Aug 17 23:07:35 GMT 2025

Total time taken to generate the page: 0.15722 seconds