X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RP_MATCHES_RCVD,SPF_NEUTRAL
X-Spam-Check-By:	sourceware.org
Message-ID:	<50F47A8B.5050001@cs.utoronto.ca>
Date:	Mon, 14 Jan 2013 16:37:15 -0500
From:	Ryan Johnson <ryan DOT johnson AT cs DOT utoronto DOT ca>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: stat() and tilde prefix (was bad bash tab completion)
References:	<5024B4D4 DOT 6080409 AT shaddybaddah DOT name> <50F395D5 DOT 4050201 AT shaddybaddah DOT name> <20130114061747 DOT GB16739 AT ednor DOT casa DOT cgf DOT cx> <20130114100002 DOT GA22039 AT calimero DOT vinschen DOT de> <50F417F9 DOT 8040108 AT shaddybaddah DOT name> <20130114161307 DOT GB8617 AT calimero DOT vinschen DOT de> <c040ca2ce35648f99318ee341647c241 AT BN1PR03MB087 DOT namprd03 DOT prod DOT outlook DOT com>
In-Reply-To:	<c040ca2ce35648f99318ee341647c241@BN1PR03MB087.namprd03.prod.outlook.com>
X-IsSubscribed:	yes
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

On 14/01/2013 3:24 PM, Stephan Mueller wrote:
> Perhaps (as you may well have already considered):
>
> - replace the path prefix by the mount point first?  (this may be naïve
>    on my part, but it's not clear to me that .. early in a path should be able
>    to influence which mount point is substituted)
If I mount something at /foo/bar/baz, then /foo/bar/baz/../../blah 
definitely shouldn't end up inside baz.

> - test directory existence of the component preceding .. before collapsing
>    (in the example above) b/.. to nothing.
> - trust that for a/b3/b2/b/../../../c, the existence test of a/b3/b2/b
>    before collapsing b/.. to nothing implies existence of b2 and b3 so no
>    further tests are needed for 'runs' of .. components with enough
>    components before them
>
> Understood that this is still going to cause a slowdown because paths with
> .. are not uncommon, but it would reduce the number of additional
> existence checks from one-per-path-component to one-per-run-of-..,
> which means none in the case of paths without .. in them.
The rest seems totally reasonable to me, FWIW.

I wouldn't put it past a Makefile (esp. one generated by autotools) or a 
gcc header search path to generate paths like: 
/a/b/c/d/../e/../f/../../../g/h (which resolves to a/g/h, if I counted 
dots correctly). Even then, though, it's "only" three checks to achieve 
posix-compliant behavior.

Ryan


--
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

- Raw text -