diff options
| author | Sverker Eriksson <[email protected]> | 2018-10-03 17:17:57 +0200 |
|---|---|---|
| committer | Sverker Eriksson <[email protected]> | 2018-10-03 19:00:53 +0200 |
| commit | 4324d0a42124a9e9be42c8bb2879db4660acb9e9 (patch) | |
| tree | f85781c0b4d9491443802bf550c714b6ea366ba4 /erts/emulator/beam/erl_lock_check.c | |
| parent | d988f91307b2922de79f92d3b9aa160ac947b44c (diff) | |
| download | otp-4324d0a42124a9e9be42c8bb2879db4660acb9e9.tar.gz otp-4324d0a42124a9e9be42c8bb2879db4660acb9e9.tar.bz2 otp-4324d0a42124a9e9be42c8bb2879db4660acb9e9.zip | |
erts: Add lock order check for route nodes
Lock order is reverse tree depth, from leafs toward root.
This solution may eventually fail if running too long
as route nodes do not increase their 'lc_order' in a join operation
when they move up in the tree.
But who runs a VM with lock-checker for such a long time?
Diffstat (limited to 'erts/emulator/beam/erl_lock_check.c')
| -rw-r--r-- | erts/emulator/beam/erl_lock_check.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/erts/emulator/beam/erl_lock_check.c b/erts/emulator/beam/erl_lock_check.c index 7cc347f810..d68ddcc748 100644 --- a/erts/emulator/beam/erl_lock_check.c +++ b/erts/emulator/beam/erl_lock_check.c @@ -93,7 +93,7 @@ static erts_lc_lock_order_t erts_lock_order[] = { { "db_tab_fix", "address" }, { "db_hash_slot", "address" }, { "erl_db_catree_base_node", "term" }, - { "erl_db_catree_route_node", "dynamic" }, + { "erl_db_catree_route_node", "index" }, { "resource_monitors", "address" }, { "driver_list", NULL }, { "proc_msgq", "pid" }, |