Messages in this thread | | | Date | Wed, 27 Sep 2006 15:57:05 +0200 | From | Ingo Molnar <> | Subject | Re: [RFC] Reverting "bd_mount_mutex" to "bd_mount_sem" |
| |
* 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |