Bug #1394

[PATCH] getcwd(3) returns wrong error codes

Added by Anonymous over 7 years ago. Updated about 7 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-



getcwd(3) returns EINVAL if the supplied buffer length is 0 or 1 and ENOMEM
(duh!) if the length is greater than 1 but can't hold pathname + 1.

POSIX expects getcwd() to return EINVAL if length is 0 and ERANGE if length is
greater than 0 but less than pathname + 1.

I attach a patch to review. I've built a kernel and running it at the moment.
So far nothing bro

getcwd.diff Magnifier (965 Bytes) Anonymous, 06/04/2009 02:00 PM


#1 Updated by Anonymous about 7 years ago

Fixed with a08a76400bd23209e8e38f4835d71e88eee3c887

Also available in: Atom PDF