X-Recipient: archive-cygwin@delorie.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=CjAULUIZayiTvb5IYQFOk+EezlMS8KMhme65npsSLazK+/E6ciguH
	jrMu8MCHERf6j9XUE/jd6ms8T1rDpoX2fJrel1MbgLq3U/x/ddvQw7I05eJv8uSw
	5xgkacjpV4N3c4O2zmhYDMzshf6pfoFd1T/zZvHuNkbbD8OD0RNuAc=
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=tcGzE776wfs5QMUFDWXVt6SxSjg=; b=NLmxi7CWSqlEazNcBS68KbxVLZoT
	pnYdL8HxDKjC8TrBGaR58UDxH570PrHgkRQyYmbS5fzgG3jhuQzojerh+qhKVpvy
	AD5BrR/Cvh28AXkh2hCDvTIAsYgSjrbTtKlU2E7ZGID93vX+3lmL+KQyAyAzqPkq
	wC18Io7cx67hSuw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-4.7 required=5.0 tests=AWL,BAYES_05,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO: calimero.vinschen.de
Date: Fri, 14 Aug 2015 15:45:52 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Shares with strange ACL settings
Message-ID: <20150814134552.GG28349@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20150812152601.GL13029@calimero.vinschen.de> <loom.20150812T172703-7@post.gmane.org> <20150812155817.GN13029@calimero.vinschen.de> <878u9g9y6b.fsf@Rainer.invalid> <20150812183220.GO13029@calimero.vinschen.de> <87vbck8h92.fsf@Rainer.invalid> <20150813163302.GB28349@calimero.vinschen.de> <20150813175302.GD28349@calimero.vinschen.de> <20150814082959.GE28349@calimero.vinschen.de> <loom.20150814T125223-728@post.gmane.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="WlEyl6ow+jlIgNUh"
Content-Disposition: inline
In-Reply-To: <loom.20150814T125223-728@post.gmane.org>
User-Agent: Mutt/1.5.23 (2014-03-12)

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

Marco, please see below in terms of L3 cache info.  Thanks,

On Aug 14 10:56, Achim Gratz wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> > I checked in the change we were talking about.  Please give the latest
> > snapshot from https://cygwin.com/snapshots/ a try.
>=20
> I've had a quick look and things look good.  I'll have to roll out the
> snapshot to our server and revert the script changes, but it seems like t=
his
> should solve the problems I've had (and that forced noacl mounts in most
> cases -- I've kept additional mounts without noacl for testing purposes t=
hat
> will now come in handy).

Cool, thanks for your quick feedback.

We should just be aware that this is ultimately a kludge.  I think I now
finally understand what would have to be done to get a generic solution
which results in correct POSIX permission evaluation for any current
user and any file ACL.  However, from some preliminary testing it seems
the generic solution has at least two downsides:

- It's slow (AuthZ code, setting up and breaking down user/group contexts
  for each checked file...)

- It would always contact the AD when trying to fetch info for AD users,
  which is bad for remote machines not or slowly connected to the AD server.

Anyway, this isn't pressing so it would be nice if you keep on testing.
I'm planning to update to 2.2.1 only after a certain pipe problem just
discussed on the #cygwin IRC channel is either fixed or settled any
other way,=20

Btw., can you please also check /proc/cpuinfo?

As discussed, Cygwin's emulation fell short on L3 cache info.  I now
added code to fetch L3 cache info as well as correct processor topology
information on Intel CPUs.  For AMD CPUs the topology and cache
info was already fine.  Linux does not show L3 cache info for AMD CPUs
afaics, so I also didn't add that to Cygwin.


Thanks,
Corinna

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

--WlEyl6ow+jlIgNUh
Content-Type: application/pgp-signature

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

iQIcBAEBCAAGBQJVzfEQAAoJEPU2Bp2uRE+gn2EP/393LOv3WNujZJ9CU8THQpvQ
aK7rHH/dehql0tngV28heAM8bUYbWC12WwgjhZFI8XARS832YM32iMm9hGLvG/fO
1mW6wnAmuniYFxxW0ZDwC95mjL4QuG4ZR6BGnFAl23/lvlNajflW7ug7NoQxoHWF
FxzJ7PPGRiMgDxbWfq38xywiQscOYPKppF+xPeKtnBd7AY6WWQLEnhf+LJ8WEtcH
fuqWnY0nAGguIOATua2YZ0BDJjLHHmZT0qA6fiVLvhY/uGSHUXXoKNxQtfa220pH
GL/tPvXYkCjKCoaB6lTEJhO1wbucOxgQZJpRsrMiL7v8A4YWPwhIFZrd+3RN6NR/
GIBdz0ei5pw7Zib95yInwNjK1ZuwhStn1Jkxi8+cuH+CmcJCUAXZq7aX01LI6OoG
/X8YxezHpF23z+VNlcD8fkNmbkGnLdiDPUAm2W22XD6DaBSHS4EyMPzPhDelYRXn
09ChvOXLgMEAVL9QXmszWMD79HSDWhzYvgwXr4vcOca8Ni8BeeQzoAQKW5EZ3CYb
nk6lsVKxCNS/gZBFRL40d4tnfiPDN8ypG9IiHIh7sPqEz6ssDNRDD5AFDg4wFjmB
WX0XnvrKzGupCIhqIGlJGM6qBXmfjojCSh9PZn/cuVt2vyPEmOlo/x5owXcPwRDj
nFX5OW6FlruGuweAmNvx
=5HLA
-----END PGP SIGNATURE-----

--WlEyl6ow+jlIgNUh--