From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: Re: Use PATH_MAX for pathname char arrays. Date: Fri, 4 Apr 2008 16:51:21 +0200 Message-ID: <20080404145121.GF4075@implementation> References: <20080404141720.GB4075@implementation> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir Fraser, le Fri 04 Apr 2008 15:30:52 +0100, a écrit : > If there are better alternatives I'd be happy to use them instead. But we > already use PATH_MAX elsewhere in the tools, so this might be a > wider-ranging cleanup than you think. That's possible indeed, I'm just making sure we try to avoid adding others :) > The original impetus for this change was due to bugchecks applied in > some cases by glibc's realpath() implementation. > But actually is realpath() deprecated anyway? Ah, right, realpath has a bad semantic indeed. The intent of SUS is to have it allocate the string if NULL is given, but that's not necessarily implemented yet. In the wild, I only know GNU/Hurd which doesn't have any PATH_MAX limit, and it happens that that one has the allocation behavior. Samuel