[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- From: Alasdair G Kergon <agk redhat com>
- To: device-mapper development <dm-devel redhat com>
- Cc: Andrew Morton <akpm osdl org>, Srinivasa DS <srinivasa in ibm com>, Ingo Molnar <mingo elte hu>, Eric Sandeen <sandeen sandeen net>, linux-kernel vger kernel org
- Subject: Re: [dm-devel] [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- Date: Tue, 7 Nov 2006 23:34:20 +0000
On Tue, Nov 07, 2006 at 03:18:08PM -0500, Mike Snitzer wrote:
> Srinivasa's description of the patch just speaks to how freeze_bdev
> and thaw_bdev are used by DM but completely skips justification for
> switching from mutex to semaphore. Why is it beneficial and/or
> necessary to use a semaphore instead of a mutex here?
This used to be a semaphore; someone changed it to a mutex; we started
getting device-mapper bug reports from people because the usage breaks the
stated semantics for a mutex; this patch puts things back while we consider
if there's a better way of doing things.
Alasdair
--
agk redhat com
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]