2009-04-06 20:01:11 -06:00
|
|
|
/*
|
|
|
|
* Copyright (C) 2007 IBM Corporation
|
|
|
|
*
|
|
|
|
* Author: Cedric Le Goater <clg@fr.ibm.com>
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU General Public License as
|
|
|
|
* published by the Free Software Foundation, version 2 of the
|
|
|
|
* License.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/nsproxy.h>
|
|
|
|
#include <linux/ipc_namespace.h>
|
|
|
|
#include <linux/sysctl.h>
|
|
|
|
|
2009-04-13 15:39:48 -06:00
|
|
|
#ifdef CONFIG_PROC_SYSCTL
|
2009-04-06 20:01:11 -06:00
|
|
|
static void *get_mq(ctl_table *table)
|
|
|
|
{
|
|
|
|
char *which = table->data;
|
|
|
|
struct ipc_namespace *ipc_ns = current->nsproxy->ipc_ns;
|
|
|
|
which = (which - (char *)&init_ipc_ns) + (char *)ipc_ns;
|
|
|
|
return which;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int proc_mq_dointvec_minmax(ctl_table *table, int write,
|
2009-09-23 16:57:19 -06:00
|
|
|
void __user *buffer, size_t *lenp, loff_t *ppos)
|
2009-04-06 20:01:11 -06:00
|
|
|
{
|
|
|
|
struct ctl_table mq_table;
|
|
|
|
memcpy(&mq_table, table, sizeof(mq_table));
|
|
|
|
mq_table.data = get_mq(table);
|
|
|
|
|
2009-09-23 16:57:19 -06:00
|
|
|
return proc_dointvec_minmax(&mq_table, write, buffer,
|
2009-04-06 20:01:11 -06:00
|
|
|
lenp, ppos);
|
|
|
|
}
|
|
|
|
#else
|
|
|
|
#define proc_mq_dointvec_minmax NULL
|
|
|
|
#endif
|
|
|
|
|
ipc/mqueue: cleanup definition names and locations
Since commit b231cca4381e ("message queues: increase range limits") on
Oct 18, 2008, calls to mq_open() that did not pass in an attribute
struct and expected to get default values for the size of the queue and
the max message size now get the system wide maximums instead of
hardwired defaults like they used to get.
This was uncovered when one of the earlier patches in this patch set
increased the default system wide maximums at the same time it increased
the hard ceiling on the system wide maximums (a customer specifically
needed the hard ceiling brought back up, the new ceiling that commit
b231cca4381e introduced was too low for their production systems). By
increasing the default maximums and not realising they were tied to any
attempt to create a message queue without an attribute struct, I had
inadvertently made it such that all message queue creation attempts
without an attribute struct were failing because the new default
maximums would create a queue that exceeded the default rlimit for
message queue bytes.
As a result, the system wide defaults were brought back down to their
previous levels, and the system wide ceilings on the maximums were
raised to meet the customer's needs. However, the fact that the no
attribute struct behavior of mq_open() could be broken by changing the
system wide maximums for message queues was seen as fundamentally broken
itself. So we hardwired the no attribute case back like it used to be.
But, then we realized that on the very off chance that some piece of
software in the wild depended on that behavior, we could work around
that issue by adding two new knobs to /proc that allowed setting the
defaults for message queues created without an attr struct separately
from the system wide maximums.
What is not an option IMO is to leave the current behavior in place. No
piece of software should ever rely on setting the system wide maximums
in order to get a desired message queue. Such a reliance would be so
fundamentally multitasking OS unfriendly as to not really be tolerable.
Fortunately, we don't know of any software in the wild that uses this
except for a regression test program that caught the issue in the first
place. If there is though, we have made accommodations with the two new
/proc knobs (and that's all the accommodations such fundamentally broken
software can be allowed)..
This patch:
The various defines for minimums and maximums of the sysctl controllable
mqueue values are scattered amongst different files and named
inconsistently. Move them all into ipc_namespace.h and make them have
consistent names. Additionally, make the number of queues per namespace
also have a minimum and maximum and use the same sysctl function as the
other two settable variables.
Signed-off-by: Doug Ledford <dledford@redhat.com>
Acked-by: Serge E. Hallyn <serue@us.ibm.com>
Cc: Amerigo Wang <amwang@redhat.com>
Cc: Joe Korty <joe.korty@ccur.com>
Cc: Jiri Slaby <jslaby@suse.cz>
Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Manfred Spraul <manfred@colorfullife.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2012-05-31 17:26:28 -06:00
|
|
|
static int msg_queues_limit_min = MIN_QUEUESMAX;
|
|
|
|
static int msg_queues_limit_max = HARD_QUEUESMAX;
|
|
|
|
|
2009-04-06 20:01:11 -06:00
|
|
|
static int msg_max_limit_min = MIN_MSGMAX;
|
ipc/mqueue: cleanup definition names and locations
Since commit b231cca4381e ("message queues: increase range limits") on
Oct 18, 2008, calls to mq_open() that did not pass in an attribute
struct and expected to get default values for the size of the queue and
the max message size now get the system wide maximums instead of
hardwired defaults like they used to get.
This was uncovered when one of the earlier patches in this patch set
increased the default system wide maximums at the same time it increased
the hard ceiling on the system wide maximums (a customer specifically
needed the hard ceiling brought back up, the new ceiling that commit
b231cca4381e introduced was too low for their production systems). By
increasing the default maximums and not realising they were tied to any
attempt to create a message queue without an attribute struct, I had
inadvertently made it such that all message queue creation attempts
without an attribute struct were failing because the new default
maximums would create a queue that exceeded the default rlimit for
message queue bytes.
As a result, the system wide defaults were brought back down to their
previous levels, and the system wide ceilings on the maximums were
raised to meet the customer's needs. However, the fact that the no
attribute struct behavior of mq_open() could be broken by changing the
system wide maximums for message queues was seen as fundamentally broken
itself. So we hardwired the no attribute case back like it used to be.
But, then we realized that on the very off chance that some piece of
software in the wild depended on that behavior, we could work around
that issue by adding two new knobs to /proc that allowed setting the
defaults for message queues created without an attr struct separately
from the system wide maximums.
What is not an option IMO is to leave the current behavior in place. No
piece of software should ever rely on setting the system wide maximums
in order to get a desired message queue. Such a reliance would be so
fundamentally multitasking OS unfriendly as to not really be tolerable.
Fortunately, we don't know of any software in the wild that uses this
except for a regression test program that caught the issue in the first
place. If there is though, we have made accommodations with the two new
/proc knobs (and that's all the accommodations such fundamentally broken
software can be allowed)..
This patch:
The various defines for minimums and maximums of the sysctl controllable
mqueue values are scattered amongst different files and named
inconsistently. Move them all into ipc_namespace.h and make them have
consistent names. Additionally, make the number of queues per namespace
also have a minimum and maximum and use the same sysctl function as the
other two settable variables.
Signed-off-by: Doug Ledford <dledford@redhat.com>
Acked-by: Serge E. Hallyn <serue@us.ibm.com>
Cc: Amerigo Wang <amwang@redhat.com>
Cc: Joe Korty <joe.korty@ccur.com>
Cc: Jiri Slaby <jslaby@suse.cz>
Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Manfred Spraul <manfred@colorfullife.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2012-05-31 17:26:28 -06:00
|
|
|
static int msg_max_limit_max = HARD_MSGMAX;
|
2009-04-06 20:01:11 -06:00
|
|
|
|
|
|
|
static int msg_maxsize_limit_min = MIN_MSGSIZEMAX;
|
ipc/mqueue: cleanup definition names and locations
Since commit b231cca4381e ("message queues: increase range limits") on
Oct 18, 2008, calls to mq_open() that did not pass in an attribute
struct and expected to get default values for the size of the queue and
the max message size now get the system wide maximums instead of
hardwired defaults like they used to get.
This was uncovered when one of the earlier patches in this patch set
increased the default system wide maximums at the same time it increased
the hard ceiling on the system wide maximums (a customer specifically
needed the hard ceiling brought back up, the new ceiling that commit
b231cca4381e introduced was too low for their production systems). By
increasing the default maximums and not realising they were tied to any
attempt to create a message queue without an attribute struct, I had
inadvertently made it such that all message queue creation attempts
without an attribute struct were failing because the new default
maximums would create a queue that exceeded the default rlimit for
message queue bytes.
As a result, the system wide defaults were brought back down to their
previous levels, and the system wide ceilings on the maximums were
raised to meet the customer's needs. However, the fact that the no
attribute struct behavior of mq_open() could be broken by changing the
system wide maximums for message queues was seen as fundamentally broken
itself. So we hardwired the no attribute case back like it used to be.
But, then we realized that on the very off chance that some piece of
software in the wild depended on that behavior, we could work around
that issue by adding two new knobs to /proc that allowed setting the
defaults for message queues created without an attr struct separately
from the system wide maximums.
What is not an option IMO is to leave the current behavior in place. No
piece of software should ever rely on setting the system wide maximums
in order to get a desired message queue. Such a reliance would be so
fundamentally multitasking OS unfriendly as to not really be tolerable.
Fortunately, we don't know of any software in the wild that uses this
except for a regression test program that caught the issue in the first
place. If there is though, we have made accommodations with the two new
/proc knobs (and that's all the accommodations such fundamentally broken
software can be allowed)..
This patch:
The various defines for minimums and maximums of the sysctl controllable
mqueue values are scattered amongst different files and named
inconsistently. Move them all into ipc_namespace.h and make them have
consistent names. Additionally, make the number of queues per namespace
also have a minimum and maximum and use the same sysctl function as the
other two settable variables.
Signed-off-by: Doug Ledford <dledford@redhat.com>
Acked-by: Serge E. Hallyn <serue@us.ibm.com>
Cc: Amerigo Wang <amwang@redhat.com>
Cc: Joe Korty <joe.korty@ccur.com>
Cc: Jiri Slaby <jslaby@suse.cz>
Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Manfred Spraul <manfred@colorfullife.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2012-05-31 17:26:28 -06:00
|
|
|
static int msg_maxsize_limit_max = HARD_MSGSIZEMAX;
|
2009-04-06 20:01:11 -06:00
|
|
|
|
|
|
|
static ctl_table mq_sysctls[] = {
|
|
|
|
{
|
|
|
|
.procname = "queues_max",
|
|
|
|
.data = &init_ipc_ns.mq_queues_max,
|
|
|
|
.maxlen = sizeof(int),
|
|
|
|
.mode = 0644,
|
ipc/mqueue: cleanup definition names and locations
Since commit b231cca4381e ("message queues: increase range limits") on
Oct 18, 2008, calls to mq_open() that did not pass in an attribute
struct and expected to get default values for the size of the queue and
the max message size now get the system wide maximums instead of
hardwired defaults like they used to get.
This was uncovered when one of the earlier patches in this patch set
increased the default system wide maximums at the same time it increased
the hard ceiling on the system wide maximums (a customer specifically
needed the hard ceiling brought back up, the new ceiling that commit
b231cca4381e introduced was too low for their production systems). By
increasing the default maximums and not realising they were tied to any
attempt to create a message queue without an attribute struct, I had
inadvertently made it such that all message queue creation attempts
without an attribute struct were failing because the new default
maximums would create a queue that exceeded the default rlimit for
message queue bytes.
As a result, the system wide defaults were brought back down to their
previous levels, and the system wide ceilings on the maximums were
raised to meet the customer's needs. However, the fact that the no
attribute struct behavior of mq_open() could be broken by changing the
system wide maximums for message queues was seen as fundamentally broken
itself. So we hardwired the no attribute case back like it used to be.
But, then we realized that on the very off chance that some piece of
software in the wild depended on that behavior, we could work around
that issue by adding two new knobs to /proc that allowed setting the
defaults for message queues created without an attr struct separately
from the system wide maximums.
What is not an option IMO is to leave the current behavior in place. No
piece of software should ever rely on setting the system wide maximums
in order to get a desired message queue. Such a reliance would be so
fundamentally multitasking OS unfriendly as to not really be tolerable.
Fortunately, we don't know of any software in the wild that uses this
except for a regression test program that caught the issue in the first
place. If there is though, we have made accommodations with the two new
/proc knobs (and that's all the accommodations such fundamentally broken
software can be allowed)..
This patch:
The various defines for minimums and maximums of the sysctl controllable
mqueue values are scattered amongst different files and named
inconsistently. Move them all into ipc_namespace.h and make them have
consistent names. Additionally, make the number of queues per namespace
also have a minimum and maximum and use the same sysctl function as the
other two settable variables.
Signed-off-by: Doug Ledford <dledford@redhat.com>
Acked-by: Serge E. Hallyn <serue@us.ibm.com>
Cc: Amerigo Wang <amwang@redhat.com>
Cc: Joe Korty <joe.korty@ccur.com>
Cc: Jiri Slaby <jslaby@suse.cz>
Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Manfred Spraul <manfred@colorfullife.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2012-05-31 17:26:28 -06:00
|
|
|
.proc_handler = proc_mq_dointvec_minmax,
|
|
|
|
.extra1 = &msg_queues_limit_min,
|
|
|
|
.extra2 = &msg_queues_limit_max,
|
2009-04-06 20:01:11 -06:00
|
|
|
},
|
|
|
|
{
|
|
|
|
.procname = "msg_max",
|
|
|
|
.data = &init_ipc_ns.mq_msg_max,
|
|
|
|
.maxlen = sizeof(int),
|
|
|
|
.mode = 0644,
|
|
|
|
.proc_handler = proc_mq_dointvec_minmax,
|
|
|
|
.extra1 = &msg_max_limit_min,
|
|
|
|
.extra2 = &msg_max_limit_max,
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.procname = "msgsize_max",
|
|
|
|
.data = &init_ipc_ns.mq_msgsize_max,
|
|
|
|
.maxlen = sizeof(int),
|
|
|
|
.mode = 0644,
|
|
|
|
.proc_handler = proc_mq_dointvec_minmax,
|
|
|
|
.extra1 = &msg_maxsize_limit_min,
|
|
|
|
.extra2 = &msg_maxsize_limit_max,
|
|
|
|
},
|
2012-05-31 17:26:33 -06:00
|
|
|
{
|
|
|
|
.procname = "msg_default",
|
|
|
|
.data = &init_ipc_ns.mq_msg_default,
|
|
|
|
.maxlen = sizeof(int),
|
|
|
|
.mode = 0644,
|
|
|
|
.proc_handler = proc_mq_dointvec_minmax,
|
|
|
|
.extra1 = &msg_max_limit_min,
|
|
|
|
.extra2 = &msg_max_limit_max,
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.procname = "msgsize_default",
|
|
|
|
.data = &init_ipc_ns.mq_msgsize_default,
|
|
|
|
.maxlen = sizeof(int),
|
|
|
|
.mode = 0644,
|
|
|
|
.proc_handler = proc_mq_dointvec_minmax,
|
|
|
|
.extra1 = &msg_maxsize_limit_min,
|
|
|
|
.extra2 = &msg_maxsize_limit_max,
|
|
|
|
},
|
2009-04-03 03:51:10 -06:00
|
|
|
{}
|
2009-04-06 20:01:11 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
static ctl_table mq_sysctl_dir[] = {
|
|
|
|
{
|
|
|
|
.procname = "mqueue",
|
|
|
|
.mode = 0555,
|
|
|
|
.child = mq_sysctls,
|
|
|
|
},
|
2009-04-03 03:51:10 -06:00
|
|
|
{}
|
2009-04-06 20:01:11 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
static ctl_table mq_sysctl_root[] = {
|
|
|
|
{
|
|
|
|
.procname = "fs",
|
|
|
|
.mode = 0555,
|
|
|
|
.child = mq_sysctl_dir,
|
|
|
|
},
|
2009-04-03 03:51:10 -06:00
|
|
|
{}
|
2009-04-06 20:01:11 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
struct ctl_table_header *mq_register_sysctl_table(void)
|
|
|
|
{
|
|
|
|
return register_sysctl_table(mq_sysctl_root);
|
|
|
|
}
|