Opened 15 years ago
Closed 15 years ago
#5005 closed bug (fixed)
Reversed Locking Order in legacy_drivers.cpp
Reported by: | bonefish | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | System/Kernel | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
legacy_drivers.cpp calls {add,remove}_node_listener() for sDriverWatcher with sLock held. DriverWatcher::EventOccured() acquires sLock, too. Since the node monitoring service has an internal lock it acquires in {add,remove}_node_listener() and also holds when calling the listeners' EventOccurred(), we have contradicting locking orders for the two cases.
Note:
See TracTickets
for help on using tickets.
Fixed in hrev35463.