[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[linux-lvm] Re: [RFC] Reverting "bd_mount_mutex" to "bd_mount_sem"
- From: Ingo Molnar <mingo elte hu>
- To: Srinivasa Ds <srinivasa in ibm com>
- Cc: dm-devel redhat com, linux-kernel vger kernel org, agk redhat com, linux-lvm redhat com
- Subject: [linux-lvm] Re: [RFC] Reverting "bd_mount_mutex" to "bd_mount_sem"
- Date: Wed, 27 Sep 2006 15:57:05 +0200
* Srinivasa Ds <srinivasa in ibm com> wrote:
> On debugging I found out that,"dmsetup suspend <device name>" calls
> "freeze_bdev()",which locks "bd_mount_mutex" to make sure that no new
> mounts happen on bdev until thaw_bdev() is called.
> This "thaw_bdev()" is getting called when we resume the device
> through "dmsetup resume <device-name>".
> Hence we have 2 processes,one of which locks
> "bd_mount_mutex"(dmsetup suspend) and Another(dmsetup resume) unlocks
> it.
hm, to me this seems quite a fragile construct - even if the
mutex-debugging warning is worked around by reverting to a semaphore.
Ingo
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]