public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oren Laadan <orenl@cs.columbia.edu>
To: MinChan Kim <minchan.kim@gmail.com>
Cc: dave@linux.vnet.ibm.com, arnd@arndb.de, jeremy@goop.org,
	linux-kernel@vger.kernel.org,
	containers@lists.linux-foundation.org
Subject: Re: [RFC v4][PATCH 2/9] General infrastructure for checkpoint restart
Date: Wed, 10 Sep 2008 14:36:16 -0400	[thread overview]
Message-ID: <48C813A0.2020404@cs.columbia.edu> (raw)
In-Reply-To: <28c262360809092310x244c0c8dvca8a6022c7d0d225@mail.gmail.com>



MinChan Kim wrote:
> On Tue, Sep 9, 2008 at 4:42 PM, Oren Laadan <orenl@cs.columbia.edu> wrote:

[...]

>> +struct cr_ctx *cr_ctx_alloc(pid_t pid, int fd, unsigned long flags)
>> +{
>> +       struct cr_ctx *ctx;
>> +
>> +       ctx = kzalloc(sizeof(*ctx), GFP_KERNEL);
>> +       if (!ctx)
>> +               return ERR_PTR(-ENOMEM);
>> +
>> +       ctx->file = fget(fd);
>> +       if (!ctx->file) {
>> +               cr_ctx_free(ctx);
>> +               return ERR_PTR(-EBADF);
>> +       }
>> +       get_file(ctx->file);
> 
> Why do you need get_file?
> You already called fget.
> Am I missing something ?

This was meant for when we will restart multiple processes, each would
have access to the checkpoint-context, such that the checkpoint-context
may outlives the task that created it and initiated the restart. Thus
the file-pointer will need to stay around longer than that task.

Of course, restart of multiple processes _can_ be coded such that this
first task will always terminate last - either after restart completes
successfully, or after all the other tasks aborted and won't use the
checkpoint-context anymore.

Because that code is not part of the this patch-set, I considered it
safer to grab a reference of the file pointer, making it less likely
that we forget about it later.

> 
>> +       ctx->hbuf = (void *) __get_free_pages(GFP_KERNEL, CR_HBUF_ORDER);
>> +       if (!ctx->hbuf) {
>> +               cr_ctx_free(ctx);
>> +               return ERR_PTR(-ENOMEM);
>> +       }
>> +
>> +       ctx->pid = pid;
>> +       ctx->flags = flags;
>> +
>> +       ctx->crid = atomic_inc_return(&cr_ctx_count);
>> +
>> +       return ctx;
>> +}

Oren.


  reply	other threads:[~2008-09-10 18:40 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 [this message]
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
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=48C813A0.2020404@cs.columbia.edu \
    --to=orenl@cs.columbia.edu \
    --cc=arnd@arndb.de \
    --cc=containers@lists.linux-foundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan.kim@gmail.com \
    /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