X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=bTWF+syYTV06L0uLHkXMiNaqIIqI3C1ZCePSQgzMoWz
	J41GsKYh+DOMu0iCCCczDEDm44xcHzCr11v0VMsjuKZVnmyym7UfyJyTCp+y8gvb
	LlvU/z+9JY/JRApiX8zm9/n72RRGaI92yK/PFbwMLsc+iO5Y4P9YhcCPHC+ZYy1U
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=007fR+lyybGWurvyGo02Rb3hh1c=; b=uoE5072aLBSfRs8qa
	3ufJNQi8/6gHbUjylqV7EZ0yRiFPNiMv/3O6Wr/S9qKM//gaDP9XRln52LP28abp
	Syj4OTQPWZSfqUJ0OgXwZWkxq6h/eL6b7DkkTTo2+Fkpb9JV3yQ1FxzYNJoSx1wl
	rUxiN3SajCUEu6JglqQbYlNnOk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO: limerock02.mail.cornell.edu
X-CornellRouted: This message has been Routed already.
Message-ID: <53FDD4A8.5050401@cornell.edu>
Date: Wed, 27 Aug 2014 08:52:56 -0400
From: Ken Brown <kbrown AT cornell DOT edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: (call-process ...) hangs in emacs
References: <20140805184047 DOT GC13601 AT calimero DOT vinschen DOT de> <53E3685B DOT 8050508 AT cornell DOT edu> <53E39BAD DOT 3010004 AT redhat DOT com> <53E3CB46 DOT 1020909 AT cornell DOT edu> <53E3F2AE DOT 7030608 AT redhat DOT com> <53E4D01B DOT 9010005 AT cornell DOT edu> <53F1F154 DOT 1020702 AT cornell DOT edu> <53FB87DC DOT 2050908 AT cornell DOT edu> <87wq9v9j2y DOT fsf AT Rainer DOT invalid> <53FD0662 DOT 5050208 AT cornell DOT edu> <20140827084245 DOT GD20700 AT calimero DOT vinschen DOT de>
In-Reply-To: <20140827084245.GD20700@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 8/27/2014 4:42 AM, Corinna Vinschen wrote:
> On Aug 26 18:12, Ken Brown wrote:
>> On 8/26/2014 2:55 PM, Achim Gratz wrote:
>>> 2) Files that have no POSIX permissions (filemode 0000) and where access
>>> is granted via ACL only get always opened as "read-only" and you have to
>>> C-x C-q them before saving.  It appears that this is Cygwin specific
>>> since on Linux the same version copes with that situation correctly
>>> (however, the mask bits in the ACL get displayed in the group portion of
>>> the file mode, which I've never seen happen on Cygwin, so this may be
>>> something that Cygwin needs to do -- maybe that'd even solve the
>>> problems that Perl has in the same situation).
>>
>> AFAICT, emacs decides whether the file is writable via the system call
>> faccessat.  (See the function 'check_writable' in src/fileio.c.)  This is
>> not Cygwin specific.  So faccessat must be returning failure in the scenario
>> you described.  I don't know if that's a Cygwin bug or not.
>
> faccessat/access/eaccess don't try to be intelligent by themselves.
> Rather they just call a Windows function if the filesystem is mounted
> with "acl" mount flags:
>
> - Fetch file's security descriptor
> - Create process impersonation token.
> - Call NtAccessCheck
> - If NtAccessCheck returns "not allowed", check for backup/restore
>    privileges via NtPrivilegeCheck.
>
> In "noacl" mode or on filesystems not supporting ACLs, access uses the
> st_mode flags from stat() to figure out the permissions.
>
> The relevant parts of the implementation are the check_file_access and
> subsequently called check_access functions in security.cc.
>
> If you see a bug there, please let me know.

Achim, could you send me a recipe for reproducing the problem so that I 
can test further?  Please be very detailed; I have no experience with ACLs.

>> BTW, emacs on Cygwin doesn't directly check ACLs, because the relevant
>> configure test fails.
>
> Works for vim.  Does the Emacs configure test only check for POSIX
> ACL functions and not for Solaris ACL functions, by any chance?

I spoke too soon.  It does detect that Cygwin has certain ACL functions. 
  But the feature that Achim was asking about seems to get used only on 
systems that have acl_get_file.  I guess that's a POSIX ACL function.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple