Re: bsd group semantics

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jeff King <peff@xxxxxxxx> writes:

> The recently added test t1301.17 is failing for me on FreeBSD; the
> created directories don't have the GID bit set.
>
> I traced this back to the fact that FORCE_DIR_SET_GID is a no-op on
> FreeBSD due to the DIR_HAS_BSD_GROUP_SEMANTICS flag being set. I am not
> sure I understand the original reasoning for this flag at all; GID seems
> to work just fine on my FreeBSD 6.1 test system.

IIRC, DIR_HAS_BSD_GROUP_SEMANTICS means you do not have to ask explicitly
with g+s to the filesystem to use the "subdirectory is owned by the same
group as its parent" semantics.  On SysV you have to ask; on BSD you do
not have to (and do not need FORCE_DIR_SET_GID).

> The original thread is here:
>
>   http://article.gmane.org/gmane.comp.version-control.git/75999

That one was not about "you do not have to ask", but "you are not allowed
to ask because the request will fail".  Perhaps between FBSD4 and FBSD6
things changed, and you can now make g+s request (which I presume is still
a no-op other than setting the bit on)?

Ideally the test should be checking if the subdirectory is owned by the
same group as the toplevel, but that is rather hard to correctly arrange,
as it depends on the set of groups the user who runs the test belongs to,
how the git work tree is set up (if it is owned by his primary group or a
secondary), etc.

For now, I'd suggest teaching the test not to care about g+s bit.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux