]> sourceware.org Git - lvm2.git/commit
Always use blocking lock for VGs and orphan locks.
authorMilan Broz <mbroz@redhat.com>
Wed, 31 Mar 2010 17:23:56 +0000 (17:23 +0000)
committerMilan Broz <mbroz@redhat.com>
Wed, 31 Mar 2010 17:23:56 +0000 (17:23 +0000)
commitb22e0a3ecba4f548041d9b9da3ea9f69dae03490
tree0a860e238d0cba01c45c9f1461ebee1a2a5f73bb
parent0802006ea76949234f7a7d0e3572e771cc0244f0
Always use blocking lock for VGs and orphan locks.

Because we have now strong rule for lock ordering:
 - VG locks must be taken in alphabetical order
 - ORPHAN locks must be the last
vgs_locked() is now not needed.

This fixes problem with orphan locking, e.g.
vgremove VG1    |    vgremove VG2
lock(VG1)       |    lock(VG2)
lock(ORPHAN)    |    lock(ORPHAN) -> fail, non-blocking

https://bugzilla.redhat.com/show_bug.cgi?id=578413

(More similar places in code.)
WHATS_NEW
lib/locking/locking.c
This page took 0.036003 seconds and 5 git commands to generate.