[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[dm-devel] Re: [PATCH 2/3] Implement generic freeze feature
- From: Andrew Morton <akpm linux-foundation org>
- To: Takashi Sato <t-sato yk jp nec com>
- Cc: "axboe kernel dk" <axboe kernel dk>, "mtk manpages googlemail com" <mtk manpages googlemail com>, "linux-kernel vger kernel org" <linux-kernel vger kernel org>, "xfs oss sgi com" <xfs oss sgi com>, Christoph Hellwig <hch infradead org>, "dm-devel redhat com" <dm-devel redhat com>, "viro ZenIV linux org uk" <viro ZenIV linux org uk>, "linux-fsdevel vger kernel org" <linux-fsdevel vger kernel org>, "linux-ext4 vger kernel org" <linux-ext4 vger kernel org>
- Subject: [dm-devel] Re: [PATCH 2/3] Implement generic freeze feature
- Date: Mon, 27 Oct 2008 23:15:33 -0700
On Mon, 27 Oct 2008 21:58:54 +0900 Takashi Sato <t-sato yk jp nec com> wrote:
> -void thaw_bdev(struct block_device *bdev, struct super_block *sb)
> +int thaw_bdev(struct block_device *bdev, struct super_block *sb)
> {
> + int error = 0;
> +
> + mutex_lock(&bdev->bd_fsfreeze_mutex);
> + if (!bdev->bd_fsfreeze_count) {
> + mutex_unlock(&bdev->bd_fsfreeze_mutex);
> + return -EINVAL;
This would be a programming error, yes?
If so, a WARN_ON is more appropriate than a silent runtime error.
> + }
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]