From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] fchmodat/fstatat: fix regression with empty `pathname`
Date: Wed, 12 Jul 2023 13:50:15 +0200 [thread overview]
Message-ID: <ZK6Td2TrKNDWZwHp@calimero.vinschen.de> (raw)
In-Reply-To: <ZKRnIfNCwKhAGi1d@calimero.vinschen.de>
Hi Johannes,
On Jul 4 20:38, Corinna Vinschen wrote:
> On Jul 4 17:45, Johannes Schindelin wrote:
> > [...]
> > BTW a colleague and I were wondering whether we really want to set
> > `errno=ENOTDIR` in `gen_full_path_at()` for empty paths when
> > `AT_EMPTY_PATH` is _not_ specified. As far as we can tell, Linux sets
> > `errno=ENOENT` in that instance.
>
> I wonder if that's really what you mean. gen_full_path_at() generates
> ENOTDIR in two scenarios:
>
> - At line 4443, if Cygwin can't resolve dirfd into a valid directory.
>
> - At line 4450 if ... actually... never. Given that p is always
> set to the end of the directory string copied into path_ret, it
> can never be NULL. Looks like this check for !p is a remnant from
> the past. We should remove it.
>
> The actual check for an empty path is done in line 4457, and this
> results in ENOENT, as desired.
>
> So, by any chance, do you mean the situation handled in line 4443,
> that is, returning ENOTDIR if dirfd doesn't resolve to a directory?
>
> Yeah, it slightly complicates the caller, but it's not exactly
> wrong, given your patch.
>
> OTOH, this entire thing doesn't look overly well thought out. We try
> to generate a full path in gen_full_path_at() and if it fails in
> a certain way and AT_EMPTY_PATH is given, we basically repeat
> trying to create a full path in the caller. Maybe some
> streamlining would be in order...
I actually found some time, to do that. So I now have a counter
proposal to your patch. I'll send the patch series in a minute. Would
you mind to take a discerning look and, perhaps, give it a try, too?
Thanks,
Corinna
next prev parent reply other threads:[~2023-07-12 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 20:51 Johannes Schindelin
2023-06-28 18:45 ` Jeremy Drake
2023-07-04 15:50 ` Johannes Schindelin
2023-07-03 10:54 ` Corinna Vinschen
2023-07-04 15:45 ` Johannes Schindelin
2023-07-04 18:38 ` Corinna Vinschen
2023-07-12 11:50 ` Corinna Vinschen [this message]
2023-07-04 15:34 ` [PATCH v2] " Johannes Schindelin
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=ZK6Td2TrKNDWZwHp@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.com \
--cc=johannes.schindelin@gmx.de \
/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).