From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cannot access system32 directory from 32 bit cygwin after the commit 456c3a46
Date: Wed, 21 Apr 2021 11:19:57 +0200 [thread overview]
Message-ID: <YH/uPeBvTfxKdRxQ@calimero.vinschen.de> (raw)
In-Reply-To: <20210421120457.cd5b6e966288aa62eee1a013@nifty.ne.jp>
Hi Takashi,
On Apr 21 12:04, Takashi Yano via Cygwin wrote:
> Hi Corinna,
>
> I noticed the problem that /cygdrive/c/Windows/System32 directory
> can be no longer accessed from 32 bit cygwin (WOW64) after the
> commit:
The problem here is the File System Redirector,
https://docs.microsoft.com/en-us/windows/win32/winprog64/file-system-redirector
This thing is really a problem because it break every, otherwise
sane assumption. Hmm, bummer. I need some time to think about
a solution here.
Thanks,
Corinna
>
> commit 456c3a46386f38887407603b2c64b7f63a4871c5
> Author: Corinna Vinschen <corinna@vinschen.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@vinschen.de>
>
> Reverting this commit resolves the issue.
>
> 64 bit cygwin does not seem to be affected. Could you please
> have a look?
>
> --
> Takashi Yano <takashi.yano@nifty.ne.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
next prev parent reply other threads:[~2021-04-21 9:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 3:04 Takashi Yano
2021-04-21 8:49 ` Andrey Repin
2021-04-21 9:10 ` Takashi Yano
2021-04-21 9:22 ` Andrey Repin
2021-04-21 10:07 ` Takashi Yano
2021-04-21 9:56 ` Marco Atzeri
2021-04-21 10:09 ` Takashi Yano
2021-04-21 9:19 ` Corinna Vinschen [this message]
2021-04-21 14:58 ` Andrey Repin
2021-04-21 15:49 ` Corinna Vinschen
2021-04-21 16:04 ` Brian Inglis
2021-04-22 8:16 ` Csaba Raduly
2021-04-22 8:26 ` Brian Inglis
2021-04-21 15:49 ` Bill Stewart
2021-04-21 16:47 ` Corinna Vinschen
2021-04-21 17:57 ` Bill Stewart
2021-04-21 19:28 ` Corinna Vinschen
2021-04-21 21:03 ` Bill Stewart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YH/uPeBvTfxKdRxQ@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).