Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754570Ab3JDKj1 (ORCPT ); Fri, 4 Oct 2013 06:39:27 -0400 Received: from relay.parallels.com ([195.214.232.42]:58456 "EHLO relay.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753406Ab3JDKj0 (ORCPT ); Fri, 4 Oct 2013 06:39:26 -0400 Message-ID: <524E9AB3.2080307@parallels.com> Date: Fri, 4 Oct 2013 14:38:43 +0400 From: Pavel Emelyanov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: Janani Venkataraman CC: , , , , , , , , , , , , , , , , , , , , , , , Subject: Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add() References: <20131004102532.1612.24185.stgit@f19-x64> In-Reply-To: <20131004102532.1612.24185.stgit@f19-x64> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.30.16.114] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 780 Lines: 24 On 10/04/2013 02:30 PM, Janani Venkataraman wrote: > Hi all, > > This series is based on the Task work add approach. We didn't adopt the CRIU > approch because of the following reasons: > > * It is not upstream yet. It is, starting from criu-v0.7 + linux-3.11 > * There are concerns about the security of the dump. Can you elaborate on this? Is it fixable in CRIU at all? > * It involves a lot of changes and this approach provides a UNIX style > interface. Can you also shed more light on this -- what changes do you mean? -- 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/