On Sat, Sep 22, 2007 at 06:07:14PM +0200, Michael Kerrisk wrote:It seems to be a dangerous idea. It has the potential of breaking userspace applications that rely on POSIX timers not creating fd's. Image code like this: /* Close stdin, stdout, stderr */ close(0); close(1); close(2); /* Oh, a timer would be nice */ timer_create(x, y, z); /* Create new stdin, stdout, stderr */ fd = open("/dev/null", flags); dup(fd); dup(fd); Unless timer_create does some magic to avoid using the lowest available fd, this would suddenly break as the timerfd would be fd 0. -- David Härdeman -
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| Faik Uygur | Re: Linux 2.6.21-rc1 |
| Ingo Molnar | [patch 02/13] syslets: add syslet.h include file, user API/ABI definitions |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: Data corruption issue with splice() on 2.6.27.10 |
| Steven Rostedt | Re: -rt scheduling: wakeup bug? |
