From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from forward105j.mail.yandex.net (forward105j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::108]) by sourceware.org (Postfix) with ESMTPS id 85E0F385E442 for ; Wed, 21 Apr 2021 09:35:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 85E0F385E442 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=yandex.ru Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=anrdaemon@yandex.ru Received: from myt6-de4b83149afa.qloud-c.yandex.net (myt6-de4b83149afa.qloud-c.yandex.net [IPv6:2a02:6b8:c12:401e:0:640:de4b:8314]) by forward105j.mail.yandex.net (Yandex) with ESMTP id 8EF6CB21EF2; Wed, 21 Apr 2021 12:35:02 +0300 (MSK) Received: from myt3-5a0d70690205.qloud-c.yandex.net (myt3-5a0d70690205.qloud-c.yandex.net [2a02:6b8:c12:4f2b:0:640:5a0d:7069]) by myt6-de4b83149afa.qloud-c.yandex.net (mxback/Yandex) with ESMTP id 13c1q1sFLo-Z2JSJQrB; Wed, 21 Apr 2021 12:35:02 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1618997702; bh=xvp/4MRxytGyoRGH452/0DzfmtkYpBQcw8Y3e+cGfZ0=; h=In-Reply-To:Subject:To:From:Message-ID:References:Date:Reply-To; b=TEeE0q2TY3yyE0qQGgi8X6Z/uxFQHKI7XvUYsweWah+ngA18CMmXqVzYyaHwgBDqA aoVy8uADQtddZvK/Yqf0Ud42y9Amp7NQ2XCfP8Btre5QHhzgpRK2xt3m9y3zlU0zmw xw+z+cGGxS8E6H/7nsCGayhsv3uVlzEdYC2hUN+Y= Authentication-Results: myt6-de4b83149afa.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru Received: by myt3-5a0d70690205.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id PW2JoLYzEh-Z1L4ATpL; Wed, 21 Apr 2021 12:35:01 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Wed, 21 Apr 2021 09:22:33 -0000 Date: Wed, 21 Apr 2021 12:22:33 +0300 From: Andrey Repin X-Mailer: The Bat! (v6.8.8) Home Reply-To: cygwin@cygwin.com X-Priority: 3 (Normal) Message-ID: <1204295812.20210421122233@yandex.ru> To: Takashi Yano , cygwin@cygwin.com Subject: Re: Cannot access system32 directory from 32 bit cygwin after the commit 456c3a46 In-Reply-To: <20210421181010.42d88c16ba3c7b1fcee68fbd@nifty.ne.jp> References: <20210421120457.cd5b6e966288aa62eee1a013@nifty.ne.jp> <1801483573.20210421114900@yandex.ru> <20210421181010.42d88c16ba3c7b1fcee68fbd@nifty.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_NUMSUBJECT, KAM_THEBAT, NICE_REPLY_A, 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@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: Wed, 21 Apr 2021 09:35:15 -0000 Greetings, Takashi Yano! > 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 >> > 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 >> >> > 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". Just curious, can you access SysNative at the same time? ls -l /proc/cygdrive/c/WINDOWS/SysNative/ -- With best regards, Andrey Repin Wednesday, April 21, 2021 12:18:51 Sorry for my terrible english...