Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753440AbYJQGbS (ORCPT ); Fri, 17 Oct 2008 02:31:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751609AbYJQGbH (ORCPT ); Fri, 17 Oct 2008 02:31:07 -0400 Received: from hawking.rebel.net.au ([203.20.69.83]:42742 "EHLO hawking.rebel.net.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751605AbYJQGbG (ORCPT ); Fri, 17 Oct 2008 02:31:06 -0400 Message-ID: <48F83121.7070705@davidnewall.com> Date: Fri, 17 Oct 2008 17:00:57 +1030 From: David Newall User-Agent: Thunderbird 2.0.0.12 (X11/20080227) MIME-Version: 1.0 To: Peter Chubb CC: Oren Laadan , Daniel Lezcano , Cedric Le Goater , jeremy@goop.org, arnd@arndb.de, containers@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Dave Hansen , linux-mm@kvack.org, Alexander Viro , "H. Peter Anvin" , Ingo Molnar , Thomas Gleixner , Andrey Mirkin Subject: Re: [RFC v6][PATCH 0/9] Kernel based checkpoint/restart References: <1223461197-11513-1-git-send-email-orenl@cs.columbia.edu> <20081009124658.GE2952@elte.hu> <1223557122.11830.14.camel@nimitz> <20081009131701.GA21112@elte.hu> <1223559246.11830.23.camel@nimitz> <20081009134415.GA12135@elte.hu> <1223571036.11830.32.camel@nimitz> <20081010153951.GD28977@elte.hu> <48F30315.1070909@fr.ibm.com> <1223916223.29877.14.camel@nimitz> <48F6092D.6050400@fr.ibm.com> <48F685A3.1060804@cs.columbia.edu> <48F7352F.3020700@fr.ibm.com> <48F74674.20202@cs.columbia.edu> <87r66g8875.wl%peter@chubb.wattle.id.au> In-Reply-To: <87r66g8875.wl%peter@chubb.wattle.id.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1301 Lines: 32 Peter Chubb wrote: >>>>>> "Oren" == Oren Laadan writes: >>>>>> > > Oren> Daniel Lezcano wrote: > > >>>> The one exception (and it is a tedious one !) are states in which >>>> the task is already frozen by definition: any ptrace blocking >>>> point where the tracee waits for the tracer to grant permission to >>>> proceed with its execution. Another example is in vfork(), waiting >>>> for completion. >>>> >>> I would say these are perfect places for "may be >>> non-checkpointable" :) >>> > > Oren> For now, yes. But we definitely want this capability in the long > Oren> run; otherwise we won't be able to checkpoint a kernel compile > Oren> ('make' uses vfork), or anything with 'gdb' running inside, or > Oren> 'strace', and other goodies. > > The strace/gdb example is *really* hard; but for vfork, you just wait > until it's over. The interval between vfork and exec/exit should be > short enough not to affect the overall time for a checkpoint A malicious user could trivially exploit that. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/