public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Oren Laadan <orenl@cs.columbia.edu>
Cc: containers@lists.linux-foundation.org, jeremy@goop.org,
	linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: Re: [RFC v4][PATCH 5/9] Memory managemnet (restore)
Date: Wed, 10 Sep 2008 12:31:23 -0700	[thread overview]
Message-ID: <1221075083.6781.34.camel@nimitz> (raw)
In-Reply-To: <1220946154-15174-6-git-send-email-orenl@cs.columbia.edu>

On Tue, 2008-09-09 at 03:42 -0400, Oren Laadan wrote:
> +/**
> + * cr_vma_read_pages_vaddrs - read addresses of pages to page-array chain
> + * @ctx - restart context
> + * @npages - number of pages
> + */
> +static int cr_vma_read_pages_vaddrs(struct cr_ctx *ctx, int npages)
> +{
> +	struct cr_pgarr *pgarr;
> +	int nr, ret;
> +
> +	while (npages) {
> +		pgarr = cr_pgarr_prep(ctx);
> +		if (!pgarr)
> +			return -ENOMEM;
> +		nr = min(npages, (int) pgarr->nr_free);
> +		ret = cr_kread(ctx, pgarr->vaddrs, nr * sizeof(unsigned long));
> +		if (ret < 0)
> +			return ret;
> +		pgarr->nr_free -= nr;
> +		pgarr->nr_used += nr;
> +		npages -= nr;
> +	}
> +	return 0;
> +}

cr_pgarr_prep() can return a partially full pgarr, right?  Won't the
cr_kread() always start at the beginning of the pgarr->vaddrs[] array?
Seems to me like it will clobber things from the last call.

-- Dave


  parent reply	other threads:[~2008-09-10 19:32 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09  7:42 [RFC v4][PATCH 0/9] Kernel based checkpoint/restart` Oren Laadan
2008-09-09  7:42 ` [RFC v4][PATCH 1/9] Create syscalls: sys_checkpoint, sys_restart Oren Laadan
2008-09-09  7:42 ` [RFC v4][PATCH 2/9] General infrastructure for checkpoint restart Oren Laadan
2008-09-10  6:10   ` MinChan Kim
2008-09-10 18:36     ` Oren Laadan
2008-09-10 22:54       ` MinChan Kim
2008-09-11  6:44         ` Oren Laadan
2008-09-09  7:42 ` [RFC v4][PATCH 3/9] x86 support for checkpoint/restart Oren Laadan
2008-09-09  8:17   ` Ingo Molnar
2008-09-09 23:23     ` Oren Laadan
2008-09-09  7:42 ` [RFC v4][PATCH 4/9] Memory management (dump) Oren Laadan
2008-09-09  9:22   ` Vegard Nossum
2008-09-10  7:51   ` MinChan Kim
2008-09-10 23:49     ` MinChan Kim
2008-09-10 16:55   ` Dave Hansen
2008-09-10 17:45     ` Dave Hansen
2008-09-10 18:28     ` Oren Laadan
2008-09-10 21:03       ` Cleanups for [PATCH " Dave Hansen
2008-09-10 21:38   ` [RFC v4][PATCH " Dave Hansen
2008-09-12 16:57   ` Dave Hansen
2008-09-09  7:42 ` [RFC v4][PATCH 5/9] Memory managemnet (restore) Oren Laadan
2008-09-09 16:07   ` Serge E. Hallyn
2008-09-09 23:35     ` Oren Laadan
2008-09-10 15:00       ` Serge E. Hallyn
2008-09-10 19:31   ` Dave Hansen [this message]
2008-09-10 19:48     ` Oren Laadan
2008-09-10 20:49       ` Dave Hansen
2008-09-11  6:59         ` Oren Laadan
2008-09-09  7:42 ` [RFC v4][PATCH 6/9] Checkpoint/restart: initial documentation Oren Laadan
2008-09-10  7:13   ` MinChan Kim
2008-09-09  7:42 ` [RFC v4][PATCH 7/9] Infrastructure for shared objects Oren Laadan
2008-09-09  7:42 ` [RFC v4][PATCH 8/9] File descriprtors (dump) Oren Laadan
2008-09-09  8:06   ` Vegard Nossum
2008-09-09  8:23   ` Vegard Nossum
2008-09-10  2:01     ` Oren Laadan
2008-09-11  5:02   ` MinChan Kim
2008-09-11  6:37     ` Oren Laadan
2008-09-09  7:42 ` [RFC v4][PATCH 9/9] File descriprtors (restore) Oren Laadan
2008-09-09 16:26   ` Dave Hansen
2008-09-10  1:49     ` Oren Laadan
2008-09-10 16:09       ` Dave Hansen
2008-09-10 18:55         ` Oren Laadan
2008-09-09 18:06 ` [RFC v4][PATCH 0/9] Kernel based checkpoint/restart` Dave Hansen

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=1221075083.6781.34.camel@nimitz \
    --to=dave@linux.vnet.ibm.com \
    --cc=arnd@arndb.de \
    --cc=containers@lists.linux-foundation.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orenl@cs.columbia.edu \
    /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