On Tue, Apr 23, 2019 at 11:31:02AM +0000, CHIGOT, CLEMENT wrote:
> From: Junio C Hamano <jch2355@xxxxxxxxx> on behalf of Junio C Hamano <gitster@xxxxxxxxx>
> This patch is needed in order to have hooks working on AIX. When run as root,
> access on hooks will return true even if a hook can't be executed. Therefore,
> as far as I know, git will try to execute it as is and we'll get this kind of
> error:
> "git commit -m content
> fatal: cannot exec '.git/hooks/pre-commit': Permission denied"
I think this is the interesting part.
What POSIX says on this is the following:
If any access permissions are checked, each shall be checked
individually, as described in XBD File Access Permissions, except that
where that description refers to execute permission for a process with
appropriate privileges, an implementation may indicate success for
X_OK even if execute permission is not granted to any user.
The XBD File Access Permissions text says:
If a process has appropriate privileges:
[…]
If execute permission is requested, access shall be granted if
execute permission is granted to at least one user by the file
permission bits or by an alternate access control mechanism;
otherwise, access shall be denied.
I believe that's what's occurring here. Your commit message, however,
should contain some text that explains that AIX takes this liberty
provided by POSIX, and why that causes problems for Git (i.e., what
problems the user will see). Ideally, the reader of the commit message
will know the relevant details about this issue from your commit message
without needing to consult the standard itself.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
Attachment:
signature.asc
Description: PGP signature
