[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <524E9AB3.2080307@parallels.com>
Date: Fri, 4 Oct 2013 14:38:43 +0400
From: Pavel Emelyanov <xemul@...allels.com>
To: Janani Venkataraman <jananive@...ibm.com>
CC: <linux-kernel@...r.kernel.org>, <amwang@...hat.com>,
<rdunlap@...otime.net>, <andi@...stfloor.org>,
<aravinda@...ux.vnet.ibm.com>, <hch@....de>, <mhiramat@...hat.com>,
<jeremy.fitzhardinge@...rix.com>, <suzuki@...ux.vnet.ibm.com>,
<kosaki.motohiro@...fujitsu.com>, <adobriyan@...il.com>,
<tarundsk@...ux.vnet.ibm.com>, <vapier@...too.org>,
<roland@...k.frob.com>, <tj@...nel.org>,
<ananth@...ux.vnet.ibm.com>, <gorcunov@...nvz.org>,
<avagin@...nvz.org>, <oleg@...hat.com>, <eparis@...hat.com>,
<d.hatayama@...fujitsu.com>, <james.hogan@...tec.com>,
<akpm@...ux-foundation.org>, <torvalds@...ux-foundation.org>
Subject: Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure
using task_work_add()
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists