Page MenuHomePhabricator

Add a "lock log" for debugging where locks are being held
ClosedPublic

Authored by epriestley on Mar 5 2018, 11:27 PM.
Tags
None
Referenced Files
F18822841: D19174.diff
Thu, Oct 23, 8:50 AM
F18764069: D19174.id45928.diff
Tue, Oct 7, 4:04 AM
F18509390: D19174.id.diff
Sep 5 2025, 3:22 AM
F18502320: D19174.diff
Sep 4 2025, 10:21 PM
F18459585: D19174.diff
Sep 1 2025, 5:26 PM
F18217669: D19174.diff
Aug 19 2025, 9:10 AM
F18094947: D19174.id.diff
Aug 7 2025, 10:26 PM
F17949883: D19174.diff
Jul 31 2025, 11:59 PM
Subscribers
None

Details

Summary

Depends on D19173. Ref T13096. Adds an optional, disabled-by-default lock log to make it easier to figure out what is acquiring and holding locks.

Test Plan

Ran bin/lock log --enable, --disable, --name, etc. Saw sensible-looking output with log enabled and daemons restarted. Saw no additional output with log disabled and daemons restarted.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Draft.Mar 6 2018, 1:55 AM
This revision was automatically updated to reflect the committed changes.