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=JTr7C+DDGF4M+gB4cGs8IKb5s0i4O3K1gcG2NgwHLY/nkya0NifgD
	hCir8r4gshr5DM/70bUG5g2xooJ0dSgY4wHV2kBns+DSWNH1lQR9XFvl+fBE4e6y
	Isw5vrGrX/64WkTTnXjaydmdKQ39wm/p6QsFNXb8/Gyfw3l7crfNK0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 10 Jul 2017 10:27:56 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.8.1-1
Message-ID: <20170710082756.GC30071@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <announce DOT 20170703133122 DOT GA1429 AT calimero DOT vinschen DOT de> <CA+kUOanF3AOhXwUzhBkunE7Nd6S7uXievc8+-QqfcsPjF9Sy+w AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="bAmEntskrkuBymla"
Content-Disposition: inline
In-Reply-To: <CA+kUOanF3AOhXwUzhBkunE7Nd6S7uXievc8+-QqfcsPjF9Sy+w@mail.gmail.com>
User-Agent: Mutt/1.8.0 (2017-02-23)

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

On Jul  7 16:07, Adam Dinwoodie wrote:
> On Mon, Jul 03, 2017 at 03:31:22PM +0200, Corinna Vinschen wrote:
> > I uploaded a new Cygwin release 2.8.1-1
>=20
> This has introduced a regression that I'm seeing when running `ls` on
> some network shares.  I can reproduce the behaviour with an install of
> only the base Cygwin packages, and the behaviour disappears if I
> downgrade back to v2.8.0-1.
>=20
> (Apologies for the obfuscation in the below report; I'm not clear on
> what I'm authorised to disclose about my work network, and so erring
> on the side of caution.)
>=20
> Specifically, if I run `ls -l` or `ls --color=3Dalways` over certain
> directories on one of my company's Windows network shares, I sometimes
> see errors stating:
>=20
>     ls: cannot access '//path/to/file/in/listed/share': Bad address
>=20
> The file that is listed in the error message appears as below in the
> `ls -l` output:
>=20
>     -?????????? ? ?                  ?                    ?
> ?  <filename>
>=20
> When this happens, the file is also coloured by `ls` as if it were not
> executable; with v2.8.0-1 the file is correctly marked as executable.
>=20
> Alternatively, in some circumstances when `ls`ing that directory, I
> see no output whatsoever.  This seems to happen in particular when
> accessing the directory via a two-hop symlink, i.e. something created
> like this:
>=20
>     $ ln -s //path/to/share symlink1
>=20
>     $ ln -s symlink1 symlink2
>=20
>     $ ls -l symlink1/
>     <list of files>
>=20
>     $ ls -l symlink2/
>=20
>     $
>=20
> The behaviour doesn't seem to be entirely consistent, and I haven't
> been able to characterise when this behaviour occurs and when it
> doesn't, even on the same directory.
>=20
> Given the behaviour seems to reliably not occur when running a bare
> `ls`, I'm guessing the problem is relating to how Cygwin is parsing
> the file permissions.

I have not been able to reproduce this.  The only relevant changes in
2.8.1 in terms of `ls' were related to reparse points (native symlinks,
directory junctions, etc) and a change of st_blocks computation related
to CompactOS compression.

For a start, can you please check if you can reproduce the problem
with the devolper snapshot from 20170606?

Also, can you reproduce this with 2.8.1 under strace perhaps? If so,
I'd be interested to see the strace output.  If you fear to compromise
company data, we can arrange to do this in private email.


Thanks,
Corinna

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

--bAmEntskrkuBymla
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJZYzqMAAoJEPU2Bp2uRE+gvrsP/02RyebNI/qoGaP/Z3+UVLU0
/a977JRAwjV54M/pZC05Sm/FnvkBdbNhrwBT8F5Xy5WurjPZ/H43X3aV74Xaxl9q
kfK5gfqMbIud5vGH3+Bxel1wut+DQ8etQpNxtPd1innJ0Hm0TE491zaGvv9rEKaC
Sw8x2MPyETgT4a3Xw0EmFFTt817q9AjAZMB/UDPF+GS3rt2YI1UJx/C+zXAQG72/
E86mx2i9f7C1hvIQZi+LgpfdncPCmF5ZKf5gKWUCTXUwlucHs9Np1SkxIlfeYgZp
YI2lLDmHDbEuV/lhkBLSDWT4C0jfVGgjGtI0zuDX7bhUW8t7cO2oIlxa4u7p0lZR
SQN9FsMF6Zm54xQaLo0X6puPc/z1Ziij6ythYRrPuYd3oLbmPNnY7n6dyItZhC82
+eEgwStarGjoNNkZmBHzfiorAQ1inFNOkFpb78ivGrWS51538+BchB2hSXB88BZG
geIVDRtDIpaQkI+SF48edcCKKUzYq3KmLpDPo3715eOYsP60QLzX/+xFoU1CYvCr
LR6VF6QzIOCttXoPtYLm7lXAnV8Ky0J8ZGCT4Ujp9wsN2Sn0AR63A9G+2wGvaHO8
o889naLs8VqbIDgM/oqKDwlAtjdqwrlU4ATVq2qqQY3GkHpz1c/mRNfO1xSLqkCD
ljUqjwMq9nb2tFVohbHz
=mCbL
-----END PGP SIGNATURE-----

--bAmEntskrkuBymla--