Re: kern/38732 (proplib has locking issues)

[David Holland <dholland-bugs%netbsd.org@localhost>]

The following reply was made to PR kern/38732; it has been noted by GNATS.

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/38732 (proplib has locking issues)
Date: Mon, 17 Oct 2016 01:14:13 +0000

 This wasn't sent to gnats.
 
    ------
 
 From: Greg Oster <oster%netbsd.org@localhost>
 To: pgoyette%NetBSD.org@localhost
 Cc: yamt%NetBSD.org@localhost, netbsd-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost
 Subject: Re: kern/38732 (proplib has locking issues)
 Date: Mon, 27 Jun 2016 09:37:58 -0600
 
 On Mon, 27 Jun 2016 11:09:28 +0000 (UTC)
 pgoyette%NetBSD.org@localhost wrote:
 
 > Synopsis: proplib has locking issues
 > 
 > State-Changed-From-To: open->analyzed
 > State-Changed-By: pgoyette%NetBSD.org@localhost
 > State-Changed-When: Mon, 27 Jun 2016 11:09:28 +0000
 > State-Changed-Why:
 > A fix for this was committed 8+ years ago, but no follow-up was done
 > (or at least, not documented in the audit trail).  So we don't know
 > if the bug was really fixed.  Set PR state to Feedback to trigger
 > notification Emails, and hopefully someone can confirm that the
 > problem is gone.  If Unless we get reports of problem still happening
 > on current code, we should just close this PR.  (The fix is old
 > enough to have already been picked up on all supported branches, so
 > no pullups are needed!)
 
 Best i can find for audit trail is this thread (mentioned in the PR):
 
 http://mail-index.netbsd.org/port-amd64/2008/05/19/msg000275.html
 
 where in this one:
 
 http://mail-index.netbsd.org/port-amd64/2008/05/20/msg000285.html
 
 it sounds like things are fixed.  
 
 I'd say call this ticket successfully resolved.
 
 Later...
 
 Greg Oster