]> 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)
committerDavid Teigland <teigland@redhat.com>
Wed, 6 Jun 2018 18:58:34 +0000 (13:58 -0500)
commitb7da704566a6542c86cc1fcc186a66aa016b6802
treed88de371b3aeca1458a8ae79ff9bd3e56261f90a
parent58a9254252a4c837601c15aabdae53d2f3c06edc
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.042387 seconds and 5 git commands to generate.