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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 22 Jun 2011 17:39:38 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Greg Kurz <gkurz@...ibm.com>
Cc:	Bryan Donlan <bdonlan@...il.com>, akpm@...ux-foundation.org,
	containers@...ts.osdl.org, linux-kernel@...r.kernel.org,
	serge@...lyn.com, daniel.lezcano@...e.fr, oleg@...hat.com,
	xemul@...nvz.org, Cedric Le Goater <clg@...t.ibm.com>
Subject: Re: [PATCH] Introduce ActivePid: in /proc/self/status (v2, was Vpid:)

Greg Kurz <gkurz@...ibm.com> writes:

> On Mon, 2011-06-20 at 15:44 -0700, Eric W. Biederman wrote:
>> fd = open("/proc/self/", O_DIRECTORY);
>> ?
>> 
>> Doing something based on proc files seems like a reasonable direction to
>> head if we are working on a race free api.
>> 
>> I suspect all we need is a sigqueue file.
>> 
>
> Are you referring to Bryan's rt_sigqueueinfo_fd() syscall or to a
> new /proc/self/sigqueue file ?

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.

Eric

--
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/