This is the mail archive of the
mailing list for the Cygwin project.
[ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.3
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 8 Sep 2015 22:54:28 +0200
- Subject: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.3
- Authentication-results: sourceware.org; auth=none
- Authentication-results: sourceware.org; auth=none
- Reply-to: cygwin at cygwin dot com
Hi Cygwin friends and users,
I released a new TEST version of Cygwin, 2.3.0-0.3.
Difference to -0.2 is just an additional fix for a potential crash in
advisory file locking observed under Wine.
So the -0.1 release message still applies:
This is the "new POSIX ACL handling reloaded" release.
In local testing I successfully integrated AuthZ into the current Cygwin
code to generate more correct user permissions by being able to generate
effective permissions for arbitrary users.
This success convinced me that it might be possible to pick up the POSIX
permission rewrite originally targeted for the 2.0.0 release and try to
update it using AuthZ and generally revamp it to reflect effective
My local testing looks good, but this is a major change, so this code
really needs a lot more testing in various scenarios. Especially
some Windows ACLs created in corporate environments are often a hard
nut to crack, and the example from
which was the ultimate downfall of the original implementation is
the stuff which needs some good testing.
There's, as usual, a downside: AuthZ leans a bit to the slow side.
Cygwin caches information already gathered once on a per-process basis,
but in locally crafted worst case scenarios (`ls' on lots of file owned
by lots of different users and groups) the slowdown may be up to 25%.
But that's really just a worst case, in the usual scenarios the slowdown
should be mostly unnoticable.
To alleviate the problem, the AuthZ code is fortunately only called for
non-Cygwin ACLs and Cygwin ACLs created before this release. Within a
pure Cygwin environment (e.g., some build directory only used with
Cygwin tools) AuthZ should be practically unused.
Apart from the aforementioned code changes to "just do it right", there
are two additional changes I implemented for this new POSIX ACL revamp
- I reverted the questionable change I added to 2.0.0-0.7 in terms of
chmod group permission handling. The original description of this
If you have a non-trivial ACL with secondary accounts and thus a
mask value, chmod is supposed to change only the mask, not the
permissions of the primary group. However, if the primary group has
few permissions to begin with, the result is really surprising. ls
-l would, e.g., show read/write perms for the group, but the group
might still have only read perms.
Personally I find this chmod behaviour really, really bad, so I took
the liberty to change it in a way which gives a much less surprising
result: If you call chmod on a non-trivial ACL, the group
permissions will be used for the primary group and the mask.
- setfacl(1) now accepts the combination of the -b and -k options, just as
on Linux (here's looking at you Achim ;)).
As for the description what this implementation strives for, please see
All changes in this release so far:
- New, unified implementation of POSIX permission and ACL handling. The
new ACLs now store the POSIX ACL MASK/CLASS_OBJ permission mask, and
they allow to inherit the S_ISGID bit. ACL inheritance now really
works as desired, in a limited, but theoretically equivalent fashion
even for non-Cygwin processes.
To accommodate Windows default ACLs, the new code ignores SYSTEM and
Administrators group permissions when computing the MASK/CLASS_OBJ
permission mask on old ACLs, and it doesn't deny access to SYSTEM and
Administrators group based on the value of MASK/CLASS_OBJ when
creating the new ACLs.
The new code now handles the S_ISGID bit on directories as on Linux:
Setting S_ISGID on a directory causes new files and subdirs created
within to inherit its group, rather than the primary group of the user
who created the file. This only works for files and directories
created by Cygwin processes.
- posix_madvise(POSIX_MADV_WILLNEED) now utilizes OS functionality available
starting with Windows 8/Server 2012. Still a no-op on older systems.
- posix_madvise(POSIX_MADV_DONTNEED) now utilizes OS functionality available
starting with Windows 8.1/Server 2012R2. Still a no-op on older systems.
- sysconf() now supports returning CPU cache information:
_SC_LEVEL1_ICACHE_SIZE, _SC_LEVEL1_ICACHE_ASSOC, _SC_LEVEL1_ICACHE_LINESIZE,
_SC_LEVEL1_DCACHE_SIZE, _SC_LEVEL1_DCACHE_ASSOC, _SC_LEVEL1_DCACHE_LINESIZE,
_SC_LEVEL2_CACHE_SIZE, _SC_LEVEL2_CACHE_ASSOC, _SC_LEVEL2_CACHE_LINESIZE,
_SC_LEVEL3_CACHE_SIZE, _SC_LEVEL3_CACHE_ASSOC, _SC_LEVEL3_CACHE_LINESIZE,
_SC_LEVEL4_CACHE_SIZE, _SC_LEVEL4_CACHE_ASSOC, _SC_LEVEL4_CACHE_LINESIZE
- setfacl(1) now allows to use the -b and -k option combined to allow reducing
an ACL to only reflect standard POSIX permissions.
- Fix a hang when stracing a forking or spawning process without activating
stracing of child processes.
- Fix long-standing potential SEGV on 32 bit Cygwin when the dynamic loader
for OS functions fails to load a function on Windows 7 or later.
Addresses: No actual bug report known.
- sysconf _SC_NPROCESSORS_CONF and _SC_NPROCESSORS_ONLN now handle more than
64 CPUs on Windows 7 and later.
- Fix a potential crash in advisory file locking due to usage of stack space
out of scope.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple