All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: [PATCH] c/r: Take uts_sem during checkpoint (v2)
Date: Fri, 17 Apr 2009 07:27:18 -0700	[thread overview]
Message-ID: <1239978438-5719-1-git-send-email-danms@us.ibm.com> (raw)

Fix the potential for breakage if our UTS changes during checkpoint
by grabbing uts_sem and copying those strings to temporary buffers.

Cc: orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org
Signed-off-by: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

Changes in v2:
  - Be less stupid about holding the system-wide uts_sem during
    checkpoint (!)
  - Don't hold it during restart
  - Hold uts_sem only while copying out the strings
  - Calculate the length of the saved buffers outside of the semaphore and
    avoid the duplicate _len variables by cleaning up the cr_hdr_utsns
    after the cr_write_string() of the two buffers
---
 checkpoint/ckpt_task.c |   25 ++++++++++++++-----------
 1 files changed, 14 insertions(+), 11 deletions(-)

diff --git a/checkpoint/ckpt_task.c b/checkpoint/ckpt_task.c
index 4d19e31..30858d2 100644
--- a/checkpoint/ckpt_task.c
+++ b/checkpoint/ckpt_task.c
@@ -171,8 +171,8 @@ static int cr_write_utsns(struct cr_ctx *ctx, struct uts_namespace *uts_ns)
 {
 	struct cr_hdr h;
 	struct cr_hdr_utsns *hh;
-	int domainname_len;
-	int nodename_len;
+	char nodename[__NEW_UTS_LEN + 1];
+	char domainname[__NEW_UTS_LEN + 1];
 	int ret;
 
 	h.type = CR_HDR_UTSNS;
@@ -182,22 +182,25 @@ static int cr_write_utsns(struct cr_ctx *ctx, struct uts_namespace *uts_ns)
 	if (!hh)
 		return -ENOMEM;
 
-	nodename_len = strlen(uts_ns->name.nodename) + 1;
-	domainname_len = strlen(uts_ns->name.domainname) + 1;
+	down_read(&uts_sem);
+	memcpy(nodename, uts_ns->name.nodename, sizeof(nodename));
+	memcpy(domainname, uts_ns->name.domainname, sizeof(nodename));
+	up_read(&uts_sem);
 
-	hh->nodename_len = nodename_len;
-	hh->domainname_len = domainname_len;
+	hh->nodename_len = strlen(nodename) + 1;
+	hh->domainname_len = strlen(domainname) + 1;
 
 	ret = cr_write_obj(ctx, &h, hh);
-	cr_hbuf_put(ctx, sizeof(*hh));
 	if (ret < 0)
-		return ret;
+		goto out;
 
-	ret = cr_write_string(ctx, uts_ns->name.nodename, nodename_len);
+	ret = cr_write_string(ctx, nodename, hh->nodename_len);
 	if (ret < 0)
-		return ret;
+		goto out;
 
-	ret = cr_write_string(ctx, uts_ns->name.domainname, domainname_len);
+	ret = cr_write_string(ctx, domainname, hh->domainname_len);
+ out:
+ 	cr_hbuf_put(ctx, sizeof(*hh));
 	return ret;
 }
 
-- 
1.5.6.3

             reply	other threads:[~2009-04-17 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 14:27 Dan Smith [this message]
     [not found] ` <1239978438-5719-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-04-17 15:05   ` [PATCH] c/r: Take uts_sem during checkpoint (v2) Serge E. Hallyn
     [not found]     ` <20090417150529.GB19129-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-04-17 15:11       ` Dan Smith
     [not found]         ` <87ab6fiabr.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2009-04-17 15:17           ` 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=1239978438-5719-1-git-send-email-danms@us.ibm.com \
    --to=danms-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.