X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Eric Blake Subject: Re: Cygwin1.dll 1.7.0-5x: RSYNC failures in close() system call on pipe file descriptors Date: Thu, 13 Aug 2009 19:52:01 +0000 (UTC) Lines: 37 Message-ID: References: <4A844A97 DOT 1050809 AT sipxx DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com cygwin sipxx.com> writes: > > - if (dup2(to_child_pipe[0], STDIN_FILENO) < 0 || > - close(to_child_pipe[1]) < 0 || > - close(from_child_pipe[0]) < 0 || > - dup2(from_child_pipe[1], STDOUT_FILENO) < 0) { > - rsyserr(FERROR, errno, "Failed to dup/close"); > + if (dup2(to_child_pipe[0], STDIN_FILENO) < 0) { > + rsyserr(FERROR, errno, "Failed to dup2(to-0)"); > exit_cleanup(RERR_IPC); > } > - if (to_child_pipe[0] != STDIN_FILENO) > - close(to_child_pipe[0]); > - if (from_child_pipe[1] != STDOUT_FILENO) > - close(from_child_pipe[1]); Ouch. rsync has a bug even without your patch: if you run rsync with stdout closed (as opposed to redirected), then to_child_pipe[0] can be 1, and you end up closing the just-duplicated from_child_pipe[1] that was copied to the new stdout. To be correct, rsync must compare to_child_pipe[0] against both 0 and 1, not just 0 (likewise for from_child_pipe[1] against both 0 and 1, not just 1). Amazing how often this type of bug reappears, too - historical cygwin has had it in the past with newlib's popen implementation (I fixed it 2006-08-22), as well as m4 1.4.13-1 having it due to code from gnulib (I fixed it 2009-07- 17). As an aside, it's interesting to note that on mingw, dup2(1,1) succeeds, but has the result of corrupting the fd, such that if you later do dup2(1,2), it hangs. But the fact that mishandled attempts to duplicate Windows handles can lead to weird bugs sure lends credence to the idea that BLODA may be making the matter worse when we duplicate an open socket handle. -- Eric Blake -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple