[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <A641066C-5E6B-459E-8244-87ECAB378583@seehuhn.de>
Date: Wed, 14 Mar 2007 09:45:09 +0000
From: Jochen Voß <voss@...huhn.de>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Roland McGrath <roland@...hat.com>,
Benjamin LaHaise <bcrl@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] avoid OPEN_MAX in SCM_MAX_FD
Hi,
On 14 Mar 2007, at 01:15, Linus Torvalds wrote:
> On Tue, 13 Mar 2007, Roland McGrath wrote:
>> Ok, fine. But PATH_MAX is a real constant that has some meaning
>> in the
>> kernel. It's perfectly correct to use PATH_MAX as a constant on a
>> system
>> like Linux that defines it and means what it says. Conversely,
>> OPEN_MAX
>> has no useful relationship with anything the kernel is doing at all.
>
> Sure. I'm just saying that some people may use OPEN_MAX the way I know
> people use PATH_MAX - whether it's what you're supposed to or not.
To contribute a data point here: searching for the regular expression
\[\ *OPEN_MAX\ *\]
on google code search [1] gives 25 hits for me. Replacing OPEN_MAX
with PATH_MAX results in "about 19,700" hits.
[1] http://www.google.com/codesearch?hl=en&q=+%5C%5B%5C+*OPEN_MAX%5C+*
%5C%5D&start=20&sa=N
I hope this helps,
Jochen
--
http://seehuhn.de/
-
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