linux-kernel - Re: [PATCH] Introduce O

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: <alpine.LFD.0.98.0705311256230.26602@woody.linux-foundation.org>
Date:	Thu, 31 May 2007 12:59:16 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Davide Libenzi <davidel@...ilserver.org>
cc:	Jakub Jelinek <jakub@...hat.com>,
	Ulrich Drepper <drepper@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/