RE: [PATCH v2 1/2] Limit dump_pipe program's permission to init for container

2016-08-11 Thread Zhao Lei
t; > > From: Andrei Vagin [mailto:ava...@gmail.com] > > > Sent: Friday, August 05, 2016 2:32 PM > > > To: Zhao Lei > > > Cc: LKML ; Linux Containers > > > ; Eric W. Biederman > > > > > > Subject: Re: [PATCH v2 1/2] Limit dump_pipe program&

Re: [PATCH v2 1/2] Limit dump_pipe program's permission to init for container

2016-08-05 Thread 'Andrei Vagin'
; To: Zhao Lei > > Cc: LKML ; Linux Containers > > ; Eric W. Biederman > > > > Subject: Re: [PATCH v2 1/2] Limit dump_pipe program's permission to init for > > container > > > > On Tue, Aug 2, 2016 at 2:08 AM, Zhao Lei wrote: > > > Currently

RE: [PATCH v2 1/2] Limit dump_pipe program's permission to init for container

2016-08-05 Thread Zhao Lei
Re: [PATCH v2 1/2] Limit dump_pipe program's permission to init for > container > > On Tue, Aug 2, 2016 at 2:08 AM, Zhao Lei wrote: > > Currently when we set core_pattern to a pipe, the pipe program is > > forked by kthread running with root's permission, and write dumpfile

Re: [PATCH v2 1/2] Limit dump_pipe program's permission to init for container

2016-08-04 Thread Andrei Vagin
On Tue, Aug 2, 2016 at 2:08 AM, Zhao Lei wrote: > Currently when we set core_pattern to a pipe, the pipe program is > forked by kthread running with root's permission, and write dumpfile > into host's filesystem. > Same thing happened for container, the dumper and dumpfile are also > in host(not i

[PATCH v2 1/2] Limit dump_pipe program's permission to init for container

2016-08-02 Thread Zhao Lei
Currently when we set core_pattern to a pipe, the pipe program is forked by kthread running with root's permission, and write dumpfile into host's filesystem. Same thing happened for container, the dumper and dumpfile are also in host(not in container). It have following program: 1: Not consistent