From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) by sourceware.org (Postfix) with ESMTPS id 483503848400; Tue, 4 May 2021 19:52:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 483503848400 Received: by mail-pf1-x431.google.com with SMTP id q2so11334pfh.13; Tue, 04 May 2021 12:52: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:references:in-reply-to:from:date :message-id:subject:to; bh=O4+DrSrY49pC3aZyjXsVrCpkJEgnjM6yC2RQ4YkLZPI=; b=MuN88Z4pkldllMzF7fZbC6MUsNQCheZ5I6adgTKqXijxstbhTsGz9GDrZNAApQDvJl IoQX4/civ+cccletIxtrGHqlloWhf1YRgYV9Azc7cFXFoYXKfGHJCwkfdvK1ZCxvZXk0 pvV03eEzjrM1Dlo0pokE1R7AQZswgKZI5/EWss8aFsrP20PsaacOeeJZDyBG0wmgkRDs gopEizDmixGiV+I7MdhMPc7pQs3q5ZGkK5ROi4+5627PAjEGUACUKILqMq2XphMWNeia d1r/pkR3GpcW6kd87ZPzIs48ntpzYe7twJQ+TwrR9Y01SbHZayhmPqhq5lpy8I21CuIT Bh4A== X-Gm-Message-State: AOAM532hED/Z+ezb0YSKxzJU12aHDuzwJwRgv9U86DKRHK1zvaq3fWlN 0CLtL4mCdJfZZ00viY7Ar4fjA7/YvXVjuKkp/x56xFmBfZE7Cw== X-Google-Smtp-Source: ABdhPJz1P80LzFXtYpgFStkPCPW5AKMWFj2ODSxkBVIx+0xydPlxOWjVKb3+1UK9vFxf6lQMuU4wsb2uhIGTjJolMa4= X-Received: by 2002:a62:dd50:0:b029:27a:69c8:55b6 with SMTP id w77-20020a62dd500000b029027a69c855b6mr25070365pff.6.1620157964873; Tue, 04 May 2021 12:52:44 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Orgad Shaneh Date: Tue, 4 May 2021 22:52:33 +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=-0.6 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, 04 May 2021 19:52:47 -0000 On Tue, Apr 27, 2021 at 8:44 AM Orgad Shaneh wrote: > > 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 Hi Corinna, This change breaks access to subst drives. Reported on MSYS2: https://github.com/msys2/msys2-runtime/pull/38#issuecomment-832160980 Can you please have a look? Please CC me when you reply. I'm not on the mailing list. Thank you, - Orgad