X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Eric Blake Subject: [1.7] old-style symlink handle leak Date: Wed, 24 Dec 2008 15:58:02 +0000 (UTC) Lines: 21 Message-ID: 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 Process Explorer shows that cygwin is leaking handles to dangling old-style symlink files during readdir. Here's a simple testcase: In cygwin 1.5: $ mkdir /cygdrive/c/leak $ ln -s nowhere linkfile In cygwin 1.7: $ cd /cygdrive/c/leak $ uname -a CYGWIN_NT-5.1 EBLAKE 1.7.0(0.190/5/3) 2008-12-23 16:07 i686 Cygwin $ echo * The glob forces bash to do a readdir, where it sees the old-style symlink created by cygwin 1.5. Thereafter, bash owns a handle to c:\leak\tmp\linkfile.lnk, because something in cygwin1.dll forgot to close it out. -- Eric Blake -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/