[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OFE96703A1.612D0E95-ON65257BFE.00379B31-65257BFE.0037FF3B@in.ibm.com>
Date: Tue, 8 Oct 2013 15:42:10 +0530
From: Janani Venkataraman1 <jananive@...ibm.com>
To: Pavel Emelyanov <xemul@...allels.com>
Cc: adobriyan@...il.com, akpm@...ux-foundation.org, amwang@...hat.com,
ananth@...ux.vnet.ibm.com, andi@...stfloor.org,
aravinda@...ux.vnet.ibm.com, avagin@...nvz.org,
d.hatayama@...fujitsu.com, eparis@...hat.com, gorcunov@...nvz.org,
hch@....de, james.hogan@...tec.com, jeremy.fitzhardinge@...rix.com,
kosaki.motohiro@...fujitsu.com, linux-kernel@...r.kernel.org,
mhiramat@...hat.com, oleg@...hat.com, rdunlap@...otime.net,
roland@...k.frob.com, suzuki@...ux.vnet.ibm.com,
tarundsk@...ux.vnet.ibm.com, tj@...nel.org,
torvalds@...ux-foundation.org, vapier@...too.org
Subject: Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure
using task_work_add()
From: Pavel Emelyanov <xemul@...allels.com>
To: Janani Venkataraman1/India/IBM@...IN,
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>
Date: 10/04/2013 04:08 PM
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?
We had a prototype ready earlier using the freezer approach.
http://lwn.net/Articles/419756/
We made a couple of minor changes to it and implemented using task work
add.
We wanted to know what the community felt about this approach.
Also in the previous RFD, Andi Kleen had mentioned a concern on the
security with
respect to the daemon approach for a self dump in CRIU.
Thanks.
Janani
--
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