Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-09 Thread Pavel Emelyanov
ia/IBM@IBMIN, > Cc: , , > , , > , , > , , > , , > , , > , , , > , , > , , , > , , > , > 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

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-09 Thread Pavel Emelyanov
: [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

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-08 Thread Janani Venkataraman1
...@redhat.com, epa...@redhat.com, d.hatay...@jp.fujitsu.com, james.ho...@imgtec.com, a...@linux-foundation.org, torva...@linux-foundation.org Date: 10/08/2013 12:26 AM Subject:Re: [RFC] [PATCH 00/19] Non disruptive application core dump

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-08 Thread Janani Venkataraman1
: [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 follo

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-08 Thread Janani Venkataraman1
, ava...@openvz.org, o...@redhat.com, epa...@redhat.com, d.hatay...@jp.fujitsu.com, james.ho...@imgtec.com, a...@linux-foundation.org, torva...@linux-foundation.org Date: 10/04/2013 04:08 PM Subject:Re: [RFC] [PATCH 00/19] Non disruptive application core dump

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-08 Thread Janani Venkataraman1
...@openvz.org, ava...@openvz.org, o...@redhat.com, epa...@redhat.com, d.hatay...@jp.fujitsu.com, james.ho...@imgtec.com, a...@linux-foundation.org, torva...@linux-foundation.org Date: 10/08/2013 12:26 AM Subject:Re: [RFC] [PATCH 00/19] Non disruptive

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-07 Thread Tejun Heo
Hello, On Fri, Oct 04, 2013 at 02:38:43PM +0400, Pavel Emelyanov wrote: > > * 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

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-07 Thread Andi Kleen
> > Couldn't they just use the new process_vm_readv() syscalls instead? > > AFAIK those do not require ptrace. > > > We need the register set and hence would need a ptrace. But the kernel needs to stop to to read the registers. Do you have data how much the latency difference is between an

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-07 Thread Oleg Nesterov
On 10/07, Suzuki K. Poulose wrote: > > On 10/04/2013 07:14 PM, Andi Kleen wrote: > > > Couldn't they just use the new process_vm_readv() syscalls instead? > > AFAIK those do not require ptrace. > > > We need the register set and hence would need a ptrace. Or the task itself can dump its

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-07 Thread Suzuki K. Poulose
On 10/04/2013 07:14 PM, Andi Kleen wrote: > On Fri, Oct 04, 2013 at 04:00:12PM +0530, Janani Venkataraman wrote: >> Hi all, >> >> The following series implements an infrastructure for capturing the core of >> an >> application without disrupting its process. > > The problem is that gcore et.al.

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-07 Thread Suzuki K. Poulose
On 10/04/2013 07:14 PM, Andi Kleen wrote: On Fri, Oct 04, 2013 at 04:00:12PM +0530, Janani Venkataraman wrote: Hi all, The following series implements an infrastructure for capturing the core of an application without disrupting its process. The problem is that gcore et.al. have to stop

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-07 Thread Oleg Nesterov
On 10/07, Suzuki K. Poulose wrote: On 10/04/2013 07:14 PM, Andi Kleen wrote: Couldn't they just use the new process_vm_readv() syscalls instead? AFAIK those do not require ptrace. We need the register set and hence would need a ptrace. Or the task itself can dump its

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-07 Thread Andi Kleen
Couldn't they just use the new process_vm_readv() syscalls instead? AFAIK those do not require ptrace. We need the register set and hence would need a ptrace. But the kernel needs to stop to to read the registers. Do you have data how much the latency difference is between an optimized

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-07 Thread Tejun Heo
Hello, On Fri, Oct 04, 2013 at 02:38:43PM +0400, Pavel Emelyanov wrote: * 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

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-04 Thread Andi Kleen
On Fri, Oct 04, 2013 at 04:00:12PM +0530, Janani Venkataraman wrote: > Hi all, > > The following series implements an infrastructure for capturing the core of > an > application without disrupting its process. The problem is that gcore et.al. have to stop the process briefly to attach and then

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-04 Thread Pavel Emelyanov
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

[RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-04 Thread Janani Venkataraman
Hi all, The following series implements an infrastructure for capturing the core of an application without disrupting its process. So ideally what we are trying to do is to export the infrastructure using /proc/pid/core. Reading the file would give an ELF Format core-dump at that instant

[RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-04 Thread Janani Venkataraman
Hi all, The following series implements an infrastructure for capturing the core of an application without disrupting its process. So ideally what we are trying to do is to export the infrastructure using /proc/pid/core. Reading the file would give an ELF Format core-dump at that instant

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-04 Thread Pavel Emelyanov
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

Re: [RFC] [PATCH 00/19] Non disruptive application core dump infrastructure using task_work_add()

2013-10-04 Thread Andi Kleen
On Fri, Oct 04, 2013 at 04:00:12PM +0530, Janani Venkataraman wrote: Hi all, The following series implements an infrastructure for capturing the core of an application without disrupting its process. The problem is that gcore et.al. have to stop the process briefly to attach and then use