From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) by sourceware.org (Postfix) with ESMTPS id 8EEE43857C74; Tue, 27 Apr 2021 05:44:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8EEE43857C74 Received: by mail-pg1-x52a.google.com with SMTP id t22so6342668pgu.0; Mon, 26 Apr 2021 22:44:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=FJ5CLQ5WKzU99jsnF7YTs+sgu/YtxJ1awTKJwVDVcDQ=; b=UbEhh8BzyScHoT9zhKgoEl753+GAtWCm8omBDsxum6lehFuBFX7f6uCETTWLor4aB3 jLx8XrLhjhYx2FrSD/THmU6Y9HWzqvyHyyyrnMleTD0f4O2USW+3G78kFfu4wK7v1LKm b68UodXTnDjhnPk6DWFLkX/p1Grh/P5jDahNXdwjOeEYlF9hE4zb26dV8T7QswECCrA7 6nJq2Ysayl8abm2eTAdkIyJUIRjD30uqPSJbASStgGtOq4hlyMJffvRe1GQpr7UJqMsT wDS8SVN6lCVEFzGqyE8lZj+MMM+xZooqfEl4qdJVszku/Ln0PBr1VQvOQhwOP7jp4f7E Ldlw== X-Gm-Message-State: AOAM5315gl9WgTI0rq3YFqN1XbXAdVfKlFyHwuQ+2+2G4sfi61UJH5r+ BXyXgpIRlBYNSRFUjGPW01GFt2XjpIxcKJQxwIcqdM8ZtBRi4A== X-Google-Smtp-Source: ABdhPJztqvB0+b95b8Pc2angOl0kPIr/ChxCJpC77BGEW5QdL6q177JERGbM+PsnCRb6MArWyjy6pkKg8A+GzwdE/pk= X-Received: by 2002:a62:e90c:0:b029:203:90f:6f34 with SMTP id j12-20020a62e90c0000b0290203090f6f34mr21442015pfh.29.1619502285172; Mon, 26 Apr 2021 22:44:45 -0700 (PDT) MIME-Version: 1.0 From: Orgad Shaneh Date: Tue, 27 Apr 2021 08:44:34 +0300 Message-ID: Subject: Re: realpath issue with native[strict] symlinks To: corinna-cygwin@cygwin.com, cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2021 05:44:48 -0000 On Apr 19 12:58, Corinna Vinschen via Cygwin wrote: > On Apr 18 10:59, Orgad Shaneh via Cygwin wrote: > I was going to write: > > Nothing we can do about without re-implementing Cygwin's path handling > from scratch. For historical reasons, POSIX paths are evaluated in a > non-POSIXy manner from right to left. If the resulting path is an > existing path, the assumption is that no inner path component is a > symlink. That's true as long as Windows didn't support > symlinks/junctions and Cygwin didn't support them. > > But now I'm writing this: > > Probably I have a workaround for this problem. I added a certain test > to the function checking the outer path component, so the checks for > path validity don't stop at the outer path component, just because > it's a valid Windows path. > > I pushed the patch and uploaded new developer snapshots to > https://cygwin.com/snapshots/ > > Please give them a try. Tried now, and it works for me. Thanks a lot! - Orgad