Ingo Molnar wrote:
> * Srinivasa Ds <[email protected]> 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
> hm, to me this seems quite a fragile construct - even if the
> mutex-debugging warning is worked around by reverting to a semaphore.
Ingo, what do you feel is fragile about this? It seems like this is a
reasonable way to go, except that maybe a down_trylock would be good if
a 2nd process tries to freeze while it's already frozen...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Video 4 Linux]
[Linux for the blind]