linux-kernel - Re: [PATCH] Introduce ActivePid: in /proc/self/status (v2, was Vpid:)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 23 Jun 2011 09:37:53 -0500
From:	Serge Hallyn <serge.hallyn@...onical.com>
To:	Greg Kurz <gkurz@...ibm.com>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Cedric Le Goater <clg@...t.ibm.com>,
	linux-kernel@...r.kernel.org, oleg@...hat.com,
	containers@...ts.osdl.org, akpm@...ux-foundation.org,
	xemul@...nvz.org, Bryan Donlan <bdonlan@...il.com>
Subject: Re: [PATCH] Introduce ActivePid: in /proc/self/status (v2, was Vpid:)

Quoting Greg Kurz (gkurz@...ibm.com):
> On Wed, 2011-06-22 at 17:39 -0700, Eric W. Biederman wrote:
> > I was suggesting implement rt_sigqueueinfo_fd as a proc file instead.
> > 
> > Getting a file descriptor api one way or another for delivering signals
> > sounds nice in principle.  I don't know if it is useful enough to
> > justify the cost of implementing and supporting it.
> > 
> 
> That's my concern: it will take some time to work it out and push it. In
> comparison, ActivePid: has no support overhead and is enough for
> userland code to relate pids betwen parent and child namespaces.
> Mitigating the race with pids is cool but it is another topic IMHO.

I think it's perfectly understandable for management / monitoring
software on the host to want to correlate pids on the host and in the
container.    And not reasonable that there is no way to do that.  This
patch makes sense.

I've carelessly deleted patch v3 from my inbox, but Greg please add
my

Acked-by: Serge Hallyn <serge.hallyn@...onical.com>

to v3 (https://lkml.org/lkml/2011/6/22/283)

thanks,
-serge
--
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/