public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: open /dev/null O_NOFOLLOW fails with ELOOP
Date: Wed, 21 Dec 2022 12:31:41 +0100	[thread overview]
Message-ID: <Y6LunfrlJ1767ND5@calimero.vinschen.de> (raw)
In-Reply-To: <Y6Lqz3O1AcAPjBRu@xps13>

Hi Glenn,

On Dec 21 06:15, gs-cygwin.com--- via Cygwin wrote:
> open /dev/null O_NOFOLLOW fails with ELOOP
> 
> Windows 10, 64-bit cygwin
> 
> Failed with my existing install, then I ran setup.exe, updated to
> latest, and my tests still failed.
> 
> a.c
> ---
> 
> #include <sys/types.h>
> #include <fcntl.h>
> #include <stdio.h>
> 
> int main (void)
> {
>     int fd = open("/dev/null", O_RDWR | O_NOFOLLOW, 0);
>     if (fd < 0)
>         perror("open(/dev/null)");
>     return fd;
> }
> 
> 
> $ gcc a.c ; ./a.exe
> open(/dev/null): Too many levels of symbolic links
> 
> While troubleshooting this, there were times where it succeeded and then
> times where it failed, though it failed most of the time.  It did not
> fail (or succeed) randomly, but seemingly in streaks.
> 
> Trying to start lighttpd seems to run into this bug reliably,
>   $ /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
> In the next release of lighttpd, I may end up omitting O_NOFOLLOW
> if __CYGWIN__ is defined.

Thanks for the report.  I think I see what's going on, stay tuned.


Thanks,
Corinna

  reply	other threads:[~2022-12-21 11:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 11:15 gs-cygwin.com
2022-12-21 11:31 ` Corinna Vinschen [this message]
2022-12-21 14:29   ` Corinna Vinschen
2022-12-21 19:32     ` gs-cygwin.com
2022-12-21 21:09       ` Corinna Vinschen

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=Y6LunfrlJ1767ND5@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).