lkml.org 
[lkml]   [2007]   [May]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Introduce O_CLOEXEC (take >2)


On Thu, 31 May 2007, Davide Libenzi wrote:
>
> What I meant, was that the vast majority of MT+exec apps wants all their
> fds (but an handfull, maybe) to be O_CLOEXEC. So a global,
> non-inheritable, per-process flag seemed the most straightforward
> solution.

I'm with Uli on this one. "Stateful" stuff is bad. It's essentially
impossible to handle with libraries - either the library would have to
explciitly always turn the state the way _it_ needs it, or the library
will do the wrogn thing.

For example, what about libraries that are used to set up stdin/stdout for
the forker?

This is not unlike floating point rounding. Having stateful rounding (like
the i387) is *stupid*. You want per-operation rounding (where *one* of the
choices may be "use default"). Exactly because libraries etc will need to
control their _own_ internal choices.

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-05-31 22:03    [from the cache]
©2003-2011 Jasper Spaans