xfs
[Top] [All Lists]

Re: [RFC PATCH 1/3] Implement generic freeze feature

To: "Christoph Hellwig" <hch@xxxxxxxxxxxxx>
Subject: Re: [RFC PATCH 1/3] Implement generic freeze feature
From: "Takashi Sato" <t-sato@xxxxxxxxxxxxx>
Date: Mon, 28 Apr 2008 21:59:55 +0900
Cc: <linux-ext4@xxxxxxxxxxxxxxx>, <xfs@xxxxxxxxxxx>, <dm-devel@xxxxxxxxxx>, <linux-fsdevel@xxxxxxxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <20080428103719.GA16030@xxxxxxxxxxxxx>
References: <20080428193123t-sato@xxxxxxxxxxxxxxx> <20080428103719.GA16030@xxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
Hi,

On Mon, Apr 28, 2008 at 07:31:23PM +0900, Takashi Sato wrote:
+ /* Initialize semaphore for freeze. */
+ sema_init(&bdev->bd_freeze_sem, 1);

The freezing process is already protected by bd_mount_sem, so I don't
think there's need for another one.

[...]
 down(&bdev->bd_mount_sem);
 sb = get_super(bdev);

I think the protection against double freezes would be better done by
using a trylock on bd_mount_sem.

bd_mount_sem can protect against only freezes and cannot protect against
unfreezes.  If multiple unfreezes run in parallel,  the multiple up() for
bd_mount_sem might occur incorrectly.

In fact after that it could be changed
from a semaphore to a simple test_and_set_bit.

I will consider using test_and_set_bit.

 error = -ENOTTY;
 break;
+
+ case FIFREEZE: {

This would be better to split intot a small helper ala ioctl_fibmap()

+ case FITHAW: {

Same here.

OK.  I will split small helper functions.

Cheers, Takashi

<Prev in Thread] Current Thread [Next in Thread>