From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: [PATCH 1/1] ipc namespace: initialize init_ipc_ns.count to 1
Date: Mon, 2 Mar 2009 19:45:04 -0600 [thread overview]
Message-ID: <20090303014503.GA25323@us.ibm.com> (raw)
Any objections to this patch?
From cfecafff4d4b1bb0f8fd49eb8e19384b34a7dc22 Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Date: Mon, 2 Mar 2009 16:40:18 -0800
Subject: [PATCH 1/1] ipc namespace: initialize init_ipc_ns.count to 1
That's one count for the init task. Nothing else pins an
ipc ns (i.e. not ipcns->mq_mnt). The only references to
init_ipc_ns are the sysctl .data calculations, which should
remain safe.
Signed-off-by: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
---
ipc/msgutil.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/ipc/msgutil.c b/ipc/msgutil.c
index e5d6da1..f095ee2 100644
--- a/ipc/msgutil.c
+++ b/ipc/msgutil.c
@@ -26,8 +26,7 @@ DEFINE_SPINLOCK(mq_lock);
* and not CONFIG_IPC_NS.
*/
struct ipc_namespace init_ipc_ns = {
- /* It's not for this patch to change, but should this be 1? */
- .count = ATOMIC_INIT(2),
+ .count = ATOMIC_INIT(1),
#ifdef CONFIG_POSIX_MQUEUE
.mq_queues_max = DFLT_QUEUESMAX,
.mq_msg_max = DFLT_MSGMAX,
--
1.5.4.3
next reply other threads:[~2009-03-03 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 1:45 Serge E. Hallyn [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-04 15:52 [PATCH 1/1] ipc namespace: initialize init_ipc_ns.count to 1 Serge E. Hallyn
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=20090303014503.GA25323@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
/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