[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH 4/5] block: make blkdev_get/put() handle exclusive access
- From: Tejun Heo <tj kernel org>
- To: Jan Kara <jack suse cz>
- Cc: shaggy linux vnet ibm com, leochen broadcom com, heiko carstens de ibm com, dm-devel redhat com, adilger kernel dilger ca, konishi ryusuke lab ntt co jp, drbd-dev lists linbit com, joel becker oracle com, hch infradead org, aelder sgi com, mfasheh suse com, joern logfs org, reiserfs-devel vger kernel org, viro zeniv linux org uk, swhiteho redhat com, chris mason oracle com, axboe kernel dk, tytso mit edu, sbranden broadcom com, petero2 telia com, linux-kernel vger kernel org, schwidefsky de ibm com, akpm linux-foundation org
- Subject: Re: [dm-devel] [PATCH 4/5] block: make blkdev_get/put() handle exclusive access
- Date: Tue, 09 Nov 2010 11:18:05 +0100
Hello,
On 11/03/2010 04:06 PM, Jan Kara wrote:
> On Mon 01-11-10 17:15:28, Tejun Heo wrote:
> The patch looks OK to me as far as ext3, ext4, and reiserfs are
> concerned. One thing I wondered about when I looked at it - does someone
> use the 'mode' argument of the blkdev_put() function (well, apart from the
> exclusive flag)? Because I've looked at a few random disk ->release()
> functions and none of them used it...
Yeah, I thought about removing @mode and make blkdev_put() take
@holder for exclusive releases. From what I can see, it doesn't seem
like any implementation cares but it's customary to have access to
@mode on ->release(), so I decided to keep it. It's rather flaky as
there's no mechanism to check or enforce it tho.
Thanks.
--
tejun
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]