Theoretically, IPC sysctl variables may be in different
namespaces and we have to register an appropriate ctl root
and new tables for each namespace.
On the other hand, the sysctl names do not differ from
namespace to namespace, and we already tuned the IPC
sysctl code to handle the multy-namespace variables.
I think, that registering tables for each namespace is
just a waste of kernel memory and unneeded code. Thus,
I just switch the IPC code to use the paths and keep
current namespaces management code as is.
Signed-off-by: Pavel Emelyanov <[email protected]>
---
diff --git a/ipc/ipc_sysctl.c b/ipc/ipc_sysctl.c
index 7f4235b..705fd82 100644
--- a/ipc/ipc_sysctl.c
+++ b/ipc/ipc_sysctl.c
@@ -161,19 +161,17 @@ static struct ctl_table ipc_kern_table[] = {
{}
};
-static struct ctl_table ipc_root_table[] = {
+static struct ctl_path ipc_root_path[] = {
{
- .ctl_name = CTL_KERN,
.procname = "kernel",
- .mode = 0555,
- .child = ipc_kern_table,
+ .ctl_name = CTL_KERN,
},
{}
};
static int __init ipc_sysctl_init(void)
{
- register_sysctl_table(ipc_root_table);
+ register_sysctl_paths(ipc_root_path, ipc_kern_table);
return 0;
}
--
1.5.3.4
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
