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]
Message-ID: <493EBD23.3020800@redhat.com>
Date:	Tue, 09 Dec 2008 13:46:59 -0500
From:	Casey Dahlin <cdahlin@...hat.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Scott James Remnant <scott@...split.com>
Subject: Re: [RFC PATCH] waitfd: file descriptor to wait on child processes

Alan Cox wrote:
>> prototype for a fourth: waitfd. It pretty much does what the name 
>> suggests: reading from it yields a series of status ints (as would be 
>> written into the second argument of waitpid) for child processes that 
>> have changed state. It takes essentially the same arguments as waitpid 
>> (for now) and supports the same set of features.
>>     
>
> This propogates the fundamental braindamage of waitpid - the fact the
> notification only works on child process trees.
>
> Here is a more elegant suggestion - use epoll, inotify and friends  fully
> on /proc process nodes.
>
> Alan
>
>
> --
> 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/
>   
Last I checked inotify was not supported in /proc, or at least most of 
it. What kind of work load is it to change that?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ