From: "René Scharfe" <l.s.r@web.de>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>, git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] abspath.c: use PATH_MAX in real_path_internal()
Date: Thu, 17 Jul 2014 19:05:41 +0200 [thread overview]
Message-ID: <53C80265.5030903@web.de> (raw)
In-Reply-To: <1405601143-31354-1-git-send-email-pclouds@gmail.com>
Am 17.07.2014 14:45, schrieb Nguyễn Thái Ngọc Duy:
> This array 'cwd' is used to store the result from getcwd() and chdir()
> back. PATH_MAX is the right constant for the job.
PATH_MAX may be better than 1024, but there can't really be a correct
constant. The actual limit depends on the file system.
> On systems with
> longer PATH_MAX (eg. 4096 on Linux), hard coding 1024 fails stuff,
> e.g. "git init".
Out of curiosity, I just created a path with over 130000 characters on
Linux. It's not actually usable but it shows that 4096 is not a real
limit on Linux. Here's how I created that insane path:
a=1234567890
x=$a$a$a$a$a
y=$x$x$x$x$x
cd /tmp
while true
do
mkdir $y || break
cd $y || break
done
pwd >/tmp/y
cd /tmp
wc -c <y
Another experiment with the program listed below shows that getcwd() on
Linux works fine with such paths if the provided buffer is large
enough, even though PATH_MAX is 4096:
#include <limits.h>
#include <stdio.h>
#include <string.h>
#include <unistd.h>
int main(int argc, char **argv)
{
char cwd[200000];
printf("PATH_MAX = %d\n", PATH_MAX);
if (getcwd(cwd, sizeof(cwd)))
printf("strlen(getcwd()) = %zu\n", strlen(cwd));
return 0;
}
> Make it static too to reduce stack usage.
Why is that needed? Is recursion involved? (Didn't find any in the
function itself after a very brief look.)
There is get_current_dir_name(), a GNU extension that allocates the
necessary memory. Perhaps we can use it instead and provide a
compatibility implementation based on getcwd() for platforms that don't
have it?
But then there's also this advice from the getcwd(3) manpage on OpenBSD:
"These routines have traditionally been used by programs to save the
name of a working directory for the purpose of returning to it. A much
faster and less error-prone method of accomplishing this is to open the
current directory (.) and use the fchdir(2) function to return."
So, how about something like this?
---
abspath.c | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/abspath.c b/abspath.c
index ca33558..7fff13a 100644
--- a/abspath.c
+++ b/abspath.c
@@ -38,10 +38,10 @@ static const char *real_path_internal(const char *path, int die_on_error)
/*
* If we have to temporarily chdir(), store the original CWD
- * here so that we can chdir() back to it at the end of the
+ * here so that we can fchdir() back to it at the end of the
* function:
*/
- char cwd[1024] = "";
+ int cwd_fd = -1;
int buf_index = 1;
@@ -80,7 +80,9 @@ static const char *real_path_internal(const char *path, int die_on_error)
}
if (*buf) {
- if (!*cwd && !getcwd(cwd, sizeof(cwd))) {
+ if (cwd_fd < 0)
+ cwd_fd = open(".", O_RDONLY);
+ if (cwd_fd < 0) {
if (die_on_error)
die_errno("Could not get current working directory");
else
@@ -142,8 +144,11 @@ static const char *real_path_internal(const char *path, int die_on_error)
retval = buf;
error_out:
free(last_elem);
- if (*cwd && chdir(cwd))
- die_errno("Could not change back to '%s'", cwd);
+ if (cwd_fd >= 0) {
+ if (fchdir(cwd_fd))
+ die_errno("Could not change back to the original working directory");
+ close(cwd_fd);
+ }
return retval;
}
--
2.0.2
next prev parent reply other threads:[~2014-07-17 17:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 12:45 [PATCH] abspath.c: use PATH_MAX in real_path_internal() Nguyễn Thái Ngọc Duy
2014-07-17 17:05 ` René Scharfe [this message]
2014-07-17 18:13 ` Junio C Hamano
2014-07-17 23:03 ` Karsten Blees
2014-07-18 10:49 ` Duy Nguyen
2014-07-18 15:08 ` René Scharfe
2014-07-19 12:51 ` Duy Nguyen
2014-07-20 0:29 ` Karsten Blees
2014-07-20 8:00 ` René Scharfe
2014-07-21 2:25 ` Jeff King
2014-07-18 11:32 ` René Scharfe
2014-07-19 23:55 ` Karsten Blees
2014-07-20 11:17 ` René Scharfe
2014-07-17 18:03 ` Junio C Hamano
2014-07-17 23:02 ` Karsten Blees
2014-07-17 23:03 ` Karsten Blees
2014-07-18 16:45 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53C80265.5030903@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).