From: Serge Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Mike Heffner <mikeh-ql8fK+M3D0TQT0dZR+AlfA@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Cedric Le Goater <legoater-GANU6spQydw@public.gmane.org>
Subject: Re: Mapping PIDs from parent->child namespaces
Date: Tue, 4 Jan 2011 14:49:29 -0600 [thread overview]
Message-ID: <20110104204929.GC3283@hallyn.com> (raw)
In-Reply-To: <4D23806C.5040806-ql8fK+M3D0TQT0dZR+AlfA@public.gmane.org>
Quoting Mike Heffner (mikeh-ql8fK+M3D0TQT0dZR+AlfA@public.gmane.org):
> On 01/04/2011 11:44 AM, Cedric Le Goater wrote:
> > we use the following patch to get the pid of a task as seen from its
> > pid namespace. It can be useful to identify tasks writing pids in files.
> >
>
> Great, I'll try it out. Has there been any interest in getting this into
> the mainline? Are there negatives to advertising child vpid's?
I see no problems offhand with that patch.
next prev parent reply other threads:[~2011-01-04 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 23:02 Mapping PIDs from parent->child namespaces Mike Heffner
[not found] ` <4D225579.6030106-ql8fK+M3D0TQT0dZR+AlfA@public.gmane.org>
2011-01-04 16:04 ` Daniel Lezcano
[not found] ` <4D23451B.6060807-GANU6spQydw@public.gmane.org>
2011-01-04 16:44 ` Cedric Le Goater
[not found] ` <4D234E77.6000605-GANU6spQydw@public.gmane.org>
2011-01-04 20:17 ` Mike Heffner
[not found] ` <4D23806C.5040806-ql8fK+M3D0TQT0dZR+AlfA@public.gmane.org>
2011-01-04 20:49 ` Serge Hallyn [this message]
2011-01-05 13:50 ` Cedric Le Goater
[not found] ` <4D24773F.8050800-GANU6spQydw@public.gmane.org>
2011-01-05 13:54 ` Cedric Le Goater
2011-01-04 22:02 ` Daniel Lezcano
2011-01-04 19:57 ` Mike Heffner
[not found] ` <4D237B9C.5060007-ql8fK+M3D0TQT0dZR+AlfA@public.gmane.org>
2011-01-04 22:13 ` Daniel Lezcano
[not found] ` <4D239B72.4000103-GANU6spQydw@public.gmane.org>
2011-01-05 4:50 ` Mike Heffner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110104204929.GC3283@hallyn.com \
--to=serge.hallyn-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=legoater-GANU6spQydw@public.gmane.org \
--cc=mikeh-ql8fK+M3D0TQT0dZR+AlfA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox