public inbox for cygwin-cvs@sourceware.org
help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org>
To: cygwin-cvs@sourceware.org
Subject: [newlib-cygwin/main] Cygwin: posix_getdents: do not clear attached DIR structure at fork(2)
Date: Fri,  1 Mar 2024 14:44:12 +0000 (GMT)	[thread overview]
Message-ID: <20240301144412.04F34385840E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=e2ea60728cf9de3085cb5f19b899d3470f2399e5

commit e2ea60728cf9de3085cb5f19b899d3470f2399e5
Author:     Corinna Vinschen <corinna@vinschen.de>
AuthorDate: Fri Mar 1 15:31:57 2024 +0100
Commit:     Corinna Vinschen <corinna@vinschen.de>
CommitDate: Fri Mar 1 15:32:39 2024 +0100

    Cygwin: posix_getdents: do not clear attached DIR structure at fork(2)
    
    The upcoming POSIX issue 8 will require that posix_getdents after
    fork() will pick up at the right spot, independently of being
    called in the parent or in the child process.  Remove the expression
    clearing out the attached DIR after fork.
    
    Signed-off-by: Corinna Vinschen <corinna@vinschen.de>

Diff:
---
 winsup/cygwin/fhandler/base.cc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/winsup/cygwin/fhandler/base.cc b/winsup/cygwin/fhandler/base.cc
index 643236751ab1..e5e9f2325fce 100644
--- a/winsup/cygwin/fhandler/base.cc
+++ b/winsup/cygwin/fhandler/base.cc
@@ -1636,7 +1636,6 @@ fhandler_base::fixup_after_fork (HANDLE parent)
   /* POSIX locks are not inherited across fork. */
   if (unique_id)
     del_my_locks (after_fork);
-  clear_getdents ();
 }
 
 void

                 reply	other threads:[~2024-03-01 14:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240301144412.04F34385840E@sourceware.org \
    --to=corinna@sourceware.org \
    --cc=cygwin-cvs@sourceware.org \
    /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).