X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0363B3AAA0EA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1618996242;
	bh=BSk1S5IS//RKFNpsi6aiUXqeUVk7lgE2gMFoLjTntrs=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=p/naDaegaPT5ufTOte8C8hU47mwTEqnsfED7/oSngJGmjdaQHHxq2gQtwo2tpFTDI
	 eSTr5kTAeWM1TzTCiSeOk9pqBh0oYveivYpvexyuSx9UdiRXreVa4W4PFsyEWSJznr
	 SRJE3QaJcZrI/naHeSqNxUAQJUEB7nRU4L1eIjEo=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org C115B3AA942E
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com 13L9A13g017311
X-Nifty-SrcIP: [124.155.50.190]
Date: Wed, 21 Apr 2021 18:10:10 +0900
To: cygwin AT cygwin DOT com
Subject: Re: Cannot access system32 directory from 32 bit cygwin after the
 commit 456c3a46
Message-Id: <20210421181010.42d88c16ba3c7b1fcee68fbd@nifty.ne.jp>
In-Reply-To: <1801483573.20210421114900@yandex.ru>
References: <20210421120457 DOT cd5b6e966288aa62eee1a013 AT nifty DOT ne DOT jp>
 <1801483573 DOT 20210421114900 AT yandex DOT ru>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT, NICE_REPLY_A,
 RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=no 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 AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

On Wed, 21 Apr 2021 11:49:00 +0300
Andrey Repin wrote:
> Greetings, Takashi Yano!
> 
> > I noticed the problem that /cygdrive/c/Windows/System32 directory
> > can be no longer accessed from 32 bit cygwin (WOW64) after the
> > commit:
> 
> > commit 456c3a46386f38887407603b2c64b7f63a4871c5
> > Author: Corinna Vinschen <corinna AT vinschen DOT de>
> > Date:   Mon Apr 19 14:49:14 2021 +0200
> 
> >     Cygwin: path_conv: Try to handle native symlinks more sanely
> 
> >     For local paths, add a check if the inner path components contain native
> >     symlinks or junctions.  Compare the incoming path with the path returned
> >     by NtQueryInformationFile(FileNameInformation).  If they differ, there
> >     must be at least one native symlink or junction in the path.  If so,
> >     treat the currently evaluated file as non-existant.  This forces
> >     path_conv::check to backtrack inner path components until we eliminated
> >     all native symlinks or junctions and have a normalized path.
> 
> >     Signed-off-by: Corinna Vinschen <corinna AT vinschen DOT de>
> 
> > Reverting this commit resolves the issue.
> 
> > 64 bit cygwin does not seem to be affected. Could you please
> > have a look?
> 
> How exactly it "can no longer be accessed" ? Is it opening WOW64 System32 or
> not opening anything at all?

If "ls /cygdrive/c/Windows/System32" is executed, the result is:
ls: cannot access '/cygdrive/c/Windows/System32': No such file or directory

Also, if try to execute "cmd.exe" in System32 directory, the result is:
bash: cmd.exe: command not found.
Of cource, /cygdrive/c/WINDOWS/system32 exists in the PATH.

So I mean "not opening anything at all".

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple