]> sourceware.org Git - lvm2.git/commit
Remove locking infrastructure from activation paths
authorDavid Teigland <teigland@redhat.com>
Tue, 5 Jun 2018 21:47:24 +0000 (16:47 -0500)
committerJoe Thornber <ejt@redhat.com>
Thu, 7 Jun 2018 15:17:04 +0000 (16:17 +0100)
commitda30b4a7865b82c05cd2be1a8eb3bca42c39abb3
tree0bee660d9924ede78bfca5f0cabcb3ef322de6c9
parent616eeba6f2b33640534e26dea43661724edf3a14
Remove locking infrastructure from activation paths

Basic LV functions:

  activate_lv(), deactivate_lv(),
  suspend_lv(), resume_lv()

were routed through the locking infrastruture on the way to:

  lv_activate_with_filter(), lv_deactivate(),
  lv_suspend_if_active(), lv_resume_if_active()

This commit removes the locking infrastructure from the
middle and calls the later functions directly from the former.

There were a couple of ancillary steps that the locking
infrastructure added along the way which are still included:

  - critical section inc/dec during suspend/resume
  - checking for active component LVs during activate

The "activation" file lock (serializing activation) has not
been kept because activation commands have been changed to
take the VG file lock exclusively which makes the activation
lock unused and unnecessary.
lib/activate/activate.c
lib/activate/activate.h
lib/locking/file_locking.c
lib/locking/locking.c
lib/locking/locking.h
This page took 0.039043 seconds and 5 git commands to generate.