From: "René Scharfe" <l.s.r@web.de>
To: Zenobiusz Kunegunda <zenobiusz.kunegunda@interia.pl>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: fatal: Could not get current working directory: Permission denied | affected 2.10,2.11,2.12, but not 1.9.5 |
Date: Sat, 11 Mar 2017 22:17:21 +0100 [thread overview]
Message-ID: <10cc42b8-0f63-2d97-8da1-2943970d63cc@web.de> (raw)
In-Reply-To: <hpulcgxossrwvfbbcvcl@zndn>
Am 09.03.2017 um 12:01 schrieb Zenobiusz Kunegunda:
> OK, I printed euids inside function calling getcwd(). Every single
> EUID is the same and have expected value. The same as any other local
> application run by this user. Permissions of every directory in the
> path are OK.
>
> /bin/pwd -P inside directory returned exact path and exited with exit
> status 0.
Weird.
I tried to reproduce the behavior on FreeBSD 10.3, unsuccessfully. I
tried with Ruby 2.2 from the ports tree and Ruby 2.3 installed with
rbenv, and with git 2.6.4 from the ports tree and a self-compiled
version of the current master branch.
You could try to bisect the issue to find which commit to git caused the
behavior change, but that will be a tedious process (compile and install
an intermediate version, run bundle install up to the point of interest
then hit Ctrl-C, clean up somehow, run "git bisect good" or "git bisect
bad" in the git source tree depending on the outcome of bundle, repeat
ca. twelve times more).
But I suspect the cause of the problem hides somewhere else. Why would
pwd(1) be able to call getcwd(3) just fine, while git gets an EPERM
error for the same call? I'm stumped.
René
next prev parent reply other threads:[~2017-03-11 21:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 16:10 fatal: Could not get current working directory: Permission denied | affected 2.10,2.11,2.12, but not 1.9.5 | Zenobiusz Kunegunda
2017-03-08 17:36 ` René Scharfe
2017-03-09 11:01 ` Zenobiusz Kunegunda
2017-03-11 21:17 ` René Scharfe [this message]
2017-03-13 12:23 ` Zenobiusz Kunegunda
2017-03-13 17:31 ` René Scharfe
2017-03-14 15:25 ` Zenobiusz Kunegunda
2017-03-13 13:23 ` Zenobiusz Kunegunda
2017-03-13 21:31 ` René Scharfe
2017-03-14 7:44 ` Zenobiusz Kunegunda
2017-03-14 17:59 ` René Scharfe
2017-03-15 9:44 ` Zenobiusz Kunegunda
2017-03-15 21:30 ` René Scharfe
2017-03-17 19:34 ` René Scharfe
2017-03-17 19:45 ` Stefan Beller
2017-03-17 21:07 ` René Scharfe
2017-03-17 22:29 ` Jeff King
2017-03-17 22:50 ` René Scharfe
2017-03-21 13:29 ` Zenobiusz Kunegunda
2017-03-21 19:04 ` René Scharfe
2017-03-22 8:30 ` Zenobiusz Kunegunda
2017-03-21 10:08 ` Zenobiusz Kunegunda
2017-03-09 11:11 ` Zenobiusz Kunegunda
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10cc42b8-0f63-2d97-8da1-2943970d63cc@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=zenobiusz.kunegunda@interia.pl \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).