[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5871495633F38949900D2BF2DC04883E5483D7@G08CNEXMBPEKD02.g08.fujitsu.local>
Date: Wed, 18 Jun 2014 08:29:56 +0000
From: "chenhanxiao@...fujitsu.com" <chenhanxiao@...fujitsu.com>
To: Michael Kerrisk <mtk.manpages@...il.com>
CC: containers <containers@...ts.linux-foundation.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Richard Weinberger <richard.weinberger@...il.com>,
Serge Hallyn <serge.hallyn@...ntu.com>,
"Oleg Nesterov" <oleg@...hat.com>,
David Howells <dhowells@...hat.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>,
Linux API <linux-api@...r.kernel.org>
Subject: RE: [PATCH] ns: introduce getnspid syscall
> -----Original Message-----
> From: mtk.linux.lists@...il.com [mailto:mtk.linux.lists@...il.com] On Behalf Of
> Michael Kerrisk
> Sent: Wednesday, June 18, 2014 2:27 AM
> To: Chen, Hanxiao/陈 晗霄
> Cc: containers; Linux Kernel; Richard Weinberger; Serge Hallyn; Oleg Nesterov;
> David Howells; Eric W. Biederman; Andrew Morton; Al Viro; Linux API; Michael
> Kerrisk-manpages
> Subject: Re: [PATCH] ns: introduce getnspid syscall
>
> Hello Chen Hanxiao
>
> On Tue, Jun 17, 2014 at 12:21 PM, Chen Hanxiao
> <chenhanxiao@...fujitsu.com> wrote:
> > We need a direct method of getting the pid inside containers.
> > If some issues occurred inside container guest, host user
> > could not know which process is in trouble just by guest pid:
> > the users of container guest only knew the pid inside containers.
> > This will bring obstacle for trouble shooting.
> >
> > int getnspid(pid_t pid, int fd1, int fd2, int pidtype);
>
> Please CC linux-api@...r.kernel.org on all patches that change the API
> that the kernel presents to user space. See
> https://www.kernel.org/doc/man-pages/linux-api-ml.html
>
> Thanks,
>
> Michael
>
>
Thanks for reminding.
- Chen
Powered by blists - more mailing lists