This is the mail archive of the libc-hacker@sourceware.org mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Fix allocation limit for getcwd syscall

From: Roland McGrath <roland at redhat dot com>
To: Andreas Schwab <schwab at suse dot de>
Cc: libc-hacker at sourceware dot org
Date: Fri, 4 Nov 2005 13:16:23 -0800 (PST)
Subject: Re: Fix allocation limit for getcwd syscall

We have bigger problems if PATH_MAX is defined but is not actually the
limit on the path name length as POSIX specifies.  If there is a larger
limit, that should be the PATH_MAX value.  If there is no limit, then
PATH_MAX should not be defined.

That said, I don't think the code should presume what the kernel
implementation does in this regard.  It should do something other than
crash when it gets ERANGE.

Follow-Ups:
- Re: Fix allocation limit for getcwd syscall
  - From: Andreas Schwab

References:
- Fix allocation limit for getcwd syscall
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]