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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=BzI5u2EOdDcKGcWGRAipJdHSMQK99K6v91cPQ7jkbR1I/kyqRDGjv
	fs6xsxKQ5SHkcXkEQFGJvLC48dmpDXJr+6mRT8ifN8tIBlcxoCxmZPFlwWF+xtTs
	AX2FQkiXQmKtBtvXxDFGZUg8uKYoHe4DhzxG9lF45c4erTsDB5sfq8=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=YeYhBtZRn7cstgodk2i3+DbEf88=; b=R6nZZSolSQkIKxvaNIx2VRY9wREo
	qWeMOBLas2kTwaLzfkOg8KSRfyU/7l04ceFom9hbkb7Bc6KMCQbXiWLG7Ha7sTV2
	bx/7p5UpgpVs/Wz0acLCa0WJSixFxn6P4FnIABsvpVBBNFck4hJJDjOE+m2zaLil
	+NSIlitz1LZIikI=
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=-0.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Wed, 11 Dec 2013 14:53:33 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Problems with Cygwin symlinks on a TrueCrypt volume
Message-ID:	<20131211135333.GC2527@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<21153 DOT 56522 DOT 988000 DOT 401372 AT woitok DOT gmail DOT com> <20131206163331 DOT GA1266 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
In-Reply-To:	<20131206163331.GA1266@calimero.vinschen.de>
User-Agent:	Mutt/1.5.21 (2010-09-15)

--aSOv3uy5xJSQbCk1
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Dec  6 17:33, Corinna Vinschen wrote:
> On Dec  6 15:18, Dr Rainer Woitok wrote:
> > Greetings,
> >=20
> > I just happened to stumble over the problem described below.
> >=20
> > Additional information:
> >=20
> >   - Windows Vista, patched this week.
> >=20
> >   - Cygwin updated this week.
> >=20
> >   - TrueCrypt downloaded and installed this week.
> > [...]
> > $ cd /g
> > $ ln -s . xx
> > $ ls -nl xx
> > lrwxrwxrwx 1 1002 513 1 2013-12-06 11:38 xx -> .
> > $ rm xx*
> > rm: cannot remove `xx': Permission denied
> > $ rm -f xx*
> > rm: cannot remove `xx': Permission denied
> > $ ls -nl xx*
> > lrwxrwxrwx 1 1002 513 1 2013-12-06 11:38 xx -> .
> > [...]
> > $ attrib -r 'g:\xx.lnk'
> > $ rm xx.lnk
> > $ ls -nl xx*
> > ls: cannot access xx*: No such file or directory
> > $=20
> > [...]
> > I really dont't know whether Windows  or TrueCrypt is incorrectly inter-
> > preting  the DOS ReadOnly attribute,  and thus  whose  fault this is.  I
> > would simply  suggest to change the code  of the  "rm" command so it ex-
> > plicitly removes  the DOS ReadOnly  attribute  before it unlinks any ob-
> > ject.
>=20
> Cygwin's unlink function already removes the R/O attribute if it exists,
> because the OS equivalent to the POSIX unlink function refuses to remove
> files with the R/O attribute set.  I assume there's some weirdness in the
> handling of the R/O attribute in TrueCrypt, but that's just speculation.
>=20
> What you can do to help this issue along:  The same as above, but run
> rm under strace:
>=20
>   $ strace -o rm.trace rm -f xx
>=20
> The -f flag drops the interactive prompt.  I added lots of debug output
> to the unlink functionality over time, so the rm.trace file should
> contain a lot of interesting details as to what's going wrong here.
> Just appand the rm.trace file to your next reply.

Per the strace your sent via PM (NtOpenFile after RtlSetCurrentTransaction
returns with STATUS_RM_NOT_ACTIVE), I created a patch which stops the
transaction if the following NtOpenFile returns with a certain set of
status codes and tries to call NtOpenFile again, outside of a
transaction.

I created a new snapshot with this patch.  Please give the latest
snapshot from http://cygwin.com/snapshots/ a try and report back.

Apart from that, there's a chance that this is a problem not related
to Cygwin's usage of a transaction on a TrueCrypt volume in the first
place.  Can you try the workaround from
http://support.microsoft.com/kb/948252 and see if that fixes the issue
with the release Cygwin DLL 1.7.27?



Thanks,
Corinna


--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--aSOv3uy5xJSQbCk1
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBAgAGBQJSqG5dAAoJEPU2Bp2uRE+g6JgP/RJFxuikhcLMtD9Ytf3uN3yG
Azv9onbPeDzsC17x5crci3VtCu3GYJUT/6Pt9kCP86ZqSLuKCPH71/3B12MXaHbk
FpjIci3ISbsUXZ+E7ryibe46t+4+VSMZ81tAxd9u1OdASYlCV1bBZZbonYR7cIty
XSsD4EllB+7ljtbKSZjDQ2fq3ic9zlR8LtlQ/6FJblQtUqIFxsjpP193Wnl/EXJF
KhpHDc0RZqdLV3f+MT0WxTLBExwKqLZQyIftJAObjOrxQ0gowWvS/m2w884LZetW
Jz29+AI9VZsC83eR50utO3NXNSERISxL7PKRtgGtPbDuGP94iDfFIhozlekmiS9o
8Q2XuolXWsNJdfBOWZp6Jhi49XNEAizuzxCoextLFd3qYbjxBKY3uLPvX8vv7uty
qabwwA+8RMV/25eReMCBHbN3BiV2Ja1BjEo6DROHbkBXS4uNuk51v/MoYzT8s3z2
x2yAe3q42B0EF2Hh0aIhmv/tN+tMXo7aQO7MPgOUQttqNs7uBUJ0wYSusqJq9Qlv
C2Mbc4JcSHcLeHBJ7cGivNl3uWANw9udR+GSJJoaT37pk79gaGAFtwMlOpi+BlH5
/vdEcvbULI0fFhqL8uQKPaLEgawvID3SRvykIOLHqA9MVdNqbNZ7xtPevb4iO5zw
mx6fUkqFWNM7lWUhl61/
=APdN
-----END PGP SIGNATURE-----

--aSOv3uy5xJSQbCk1--

- Raw text -