From: corinna-cygwin@cygwin.com
To: cygwin-patches@cygwin.com
Subject: [PATCH 0/2] Fix a bad case of absolute path handling
Date: Wed, 10 Nov 2021 21:32:51 +0100 [thread overview]
Message-ID: <20211110203253.2933679-1-corinna-cygwin@cygwin.com> (raw)
From: Corinna Vinschen <corinna@vinschen.de>
As I told Takashi in PM, I will try to more often send patches to the
cygwin-patches ML before pushing them, so there's a chance to chime in.
This patch series is supposed to address the `rm -rf' problem reported
in https://cygwin.com/pipermail/cygwin/2021-November/249837.html
It was always frustrating, having to allow DOS drive letter paths for
backward compatibility. This here is another case of ambiguity,
triggered by the `isabspath' macro handling "X:" as absolute path, even
without the trailing slash or backslash.
Check out the 2nd patch for a more detailed description.
While at it, I wonder if we might have a chance to fix these ambiguities
in a better way. For instance, consider this:
$ mkdir -p test/c:
$ cd test
As non-admin:
$ touch c:/foo
touch: cannot touch 'c:/foo': Permission denied
As admin, even worse:
$ touch c:/foo
$ ls /cygdrive/c/foo
foo
As long as we support DOS paths as input, I have a hard time to see how
to fix this, but maybe we can at least minimize the ambiguity somehow.
Corinna
Corinna Vinschen (2):
Cygwin: drop unused isabspath_u and iswabspath macros
Cygwin: introduce isabspath_strict macro
winsup/cygwin/syscalls.cc | 2 +-
winsup/cygwin/winsup.h | 20 ++++++++------------
2 files changed, 9 insertions(+), 13 deletions(-)
--
2.31.1
next reply other threads:[~2021-11-10 20:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 20:32 corinna-cygwin [this message]
2021-11-10 20:32 ` [PATCH 1/2] Cygwin: drop unused isabspath_u and iswabspath macros corinna-cygwin
2021-11-10 20:32 ` [PATCH 2/2] Cygwin: introduce isabspath_strict macro corinna-cygwin
2021-11-10 22:22 ` [PATCH 0/2] Fix a bad case of absolute path handling Ken Brown
2021-11-11 9:47 ` Corinna Vinschen
2021-11-11 14:10 ` Ken Brown
2021-11-12 16:30 ` Brian Inglis
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=20211110203253.2933679-1-corinna-cygwin@cygwin.com \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@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).