Linux Container Development
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [PATCH user-cr] handle the container configuration section in ckpt	header
Date: Fri, 16 Oct 2009 20:04:00 -0400	[thread overview]
Message-ID: <4AD909F0.80104@librato.com> (raw)
In-Reply-To: <20091015184859.GA30490-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>


Applied.

Serge E. Hallyn wrote:
> Signed-off-by: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> ---
>  restart.c |   29 +++++++++++++++++++++++++++++
>  1 files changed, 29 insertions(+), 0 deletions(-)
> 
> diff --git a/restart.c b/restart.c
> index e6e72ac..cb81293 100644
> --- a/restart.c
> +++ b/restart.c
> @@ -264,6 +264,7 @@ struct ckpt_ctx {
>  	
>  	char header[BUFSIZE];
>  	char header_arch[BUFSIZE];
> +	char container[BUFSIZE];
>  	char tree[BUFSIZE];
>  	char buf[BUFSIZE];
>  	struct args *args;
> @@ -303,6 +304,7 @@ static int ckpt_write_obj(struct ckpt_ctx *ctx, struct ckpt_hdr *h);
>  
>  static int ckpt_write_header(struct ckpt_ctx *ctx);
>  static int ckpt_write_header_arch(struct ckpt_ctx *ctx);
> +static int ckpt_write_container(struct ckpt_ctx *ctx);
>  static int ckpt_write_tree(struct ckpt_ctx *ctx);
>  
>  static int _ckpt_read(int fd, void *buf, int count);
> @@ -313,6 +315,7 @@ static int ckpt_read_obj_type(struct ckpt_ctx *ctx, void *b, int n, int type);
>  
>  static int ckpt_read_header(struct ckpt_ctx *ctx);
>  static int ckpt_read_header_arch(struct ckpt_ctx *ctx);
> +static int ckpt_read_container(struct ckpt_ctx *ctx);
>  static int ckpt_read_tree(struct ckpt_ctx *ctx);
>  
>  static int hash_init(struct ckpt_ctx *ctx);
> @@ -693,6 +696,12 @@ int main(int argc, char *argv[])
>  		exit(1);
>  	}
>  
> +	ret = ckpt_read_container(&ctx);
> +	if (ret < 0) {
> +		perror("read c/r container section");
> +		exit(1);
> +	}
> +
>  	ret = ckpt_read_tree(&ctx);
>  	if (ret < 0) {
>  		perror("read c/r tree");
> @@ -1850,6 +1859,9 @@ static int ckpt_do_feeder(void *data)
>  	if (ckpt_write_header_arch(ctx) < 0)
>  		ckpt_abort(ctx, "write c/r header arch");
>  
> +	if (ckpt_write_container(ctx) < 0)
> +		ckpt_abort(ctx, "write container section");
> +
>  	if (ckpt_write_tree(ctx) < 0)
>  		ckpt_abort(ctx, "write c/r tree");
>  
> @@ -2102,6 +2114,14 @@ static int ckpt_read_header_arch(struct ckpt_ctx *ctx)
>  	return 0;
>  }
>  
> +static int ckpt_read_container(struct ckpt_ctx *ctx)
> +{
> +	struct ckpt_hdr_container *h;
> +
> +	h = (struct ckpt_hdr_container *) ctx->container;
> +	return ckpt_read_obj_type(ctx, h, sizeof(*h), CKPT_HDR_CONTAINER);
> +}
> +
>  static int ckpt_read_tree(struct ckpt_ctx *ctx)
>  {
>  	struct ckpt_hdr_tree *h;
> @@ -2174,6 +2194,15 @@ static int ckpt_write_header_arch(struct ckpt_ctx *ctx)
>  	return ckpt_write_obj(ctx, (struct ckpt_hdr *) h);
>  }
>  
> +static int ckpt_write_container(struct ckpt_ctx *ctx)
> +{
> +	char *ptr;
> +
> +	ptr = (char *) ctx->container;
> +	/* write the container info section */
> +	return ckpt_write_obj(ctx, (struct ckpt_hdr *) ptr);
> +}
> +
>  static int ckpt_write_tree(struct ckpt_ctx *ctx)
>  {
>  	struct ckpt_hdr_tree *h;

  parent reply	other threads:[~2009-10-17  0:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15 18:48 [PATCH] cr: add container configuration header Serge E. Hallyn
     [not found] ` <20091015184827.GA30444-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-10-15 18:48   ` [PATCH user-cr] handle the container configuration section in ckpt header Serge E. Hallyn
     [not found]     ` <20091015184859.GA30490-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-10-17  0:04       ` Oren Laadan [this message]
2009-10-17  0:04   ` [PATCH] cr: add container configuration header Oren Laadan

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=4AD909F0.80104@librato.com \
    --to=orenl-rdfvbdnroixbdgjk7y7tuq@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@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