getting the user_data associated with an object path
hp at redhat.com
Wed Mar 23 13:43:55 PST 2005
On Wed, 2005-03-23 at 15:13 -0500, Daniel Reed wrote:
> Are there any better methods, or can this patch be reviewed?
Can you explain the use-case?
> The original patch is archived at:
The object_tree_get_user_data() function should be called
get_user_data_unlocked() if it assumes the lock is held and does not
change the lock, or get_user_data_and_unlock() if it assumes the lock is
held and unlocks it.
You can't access the "subtree" variable after unlocking, so you should
instead have a user_data variable that stores the user data directly.
More information about the dbus