Bug 9715 - The info() operation should use the activity_lock
: The info() operation should use the activity_lock
Status: RESOLVED FIXINSOURCE
Product: pkg
api-python
: unspecified
: ANY/Generic All
: P3 normal (vote)
: ---
Assigned To: johansen
: pkg/api-python watcher
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2009-06-26 12:15 UTC by johansen
Modified: 2009-07-01 16:40 UTC (History)
0 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description johansen 2009-06-26 12:15:28 UTC
In the client API, the info() operation doesn't use the activity_lock.  It
should.
Comment 1 johansen 2009-06-26 12:16:05 UTC
Wrap the call to info() with an activity_lock_acquire/release.
Comment 2 johansen 2009-06-26 12:46:47 UTC
The most current transport webrev contains this fix.

http://cr.opensolaris.org/~johansen/webrev-xport-2/
Comment 3 johansen 2009-07-01 16:40:07 UTC
Integrated 1Jul2009 as change set a48bee2a4b2e9c8345c29acea63116acf77dddb3