Re: [RFC] Reverting "bd_mount_mutex" to "bd_mount_sem"

* 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 
> 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [RFC] Reverting "bd_mount_mutex" to "bd_mount_sem"
    • From: Srinivasa Ds <[email protected]>

• Prev by Date: Re: [PATCH] move put_task_struct() reaping into a thread [Re: 2.6.18-rt1]
• Next by Date: Re: 2.6.18-mm1
• Previous by thread: [RFC] Reverting "bd_mount_mutex" to "bd_mount_sem"
• Next by thread: Re: A little script help please .... USB Keychain Drives
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]