[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080701080844.GA16691@infradead.org>
Date: Tue, 1 Jul 2008 04:08:44 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Takashi Sato <t-sato@...jp.nec.com>
Cc: akpm@...ux-foundation.org, viro@...IV.linux.org.uk,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"xfs@....sgi.com" <xfs@....sgi.com>,
"dm-devel@...hat.com" <dm-devel@...hat.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
axboe@...nel.dk, mtk.manpages@...glemail.com
Subject: Re: [PATCH 1/3] Implement generic freeze feature
> {
> struct super_block *sb;
>
> + if (test_and_set_bit(BD_FREEZE_OP, &bdev->bd_state))
> + return ERR_PTR(-EBUSY);
> +
> + sb = get_super(bdev);
> +
> + /* If super_block has been already frozen, return. */
> + if (sb && sb->s_frozen != SB_UNFROZEN) {
> + drop_super(sb);
> + clear_bit(BD_FREEZE_OP, &bdev->bd_state);
> + return sb;
> + }
> +
> + if (sb)
> + drop_super(sb);
> +
> down(&bdev->bd_mount_sem);
> sb = get_super(bdev);
> if (sb && !(sb->s_flags & MS_RDONLY)) {
> @@ -219,6 +234,8 @@ struct super_block *freeze_bdev(struct b
> }
>
> sync_blockdev(bdev);
> + clear_bit(BD_FREEZE_OP, &bdev->bd_state);
> +
Please only clear BD_FREEZE_OP in thaw_bdev, that way you can also get
rid of the frozen check above, and the double-get_super. Also
bd_mount_sem could be removed that way by checking for BD_FREEZE_OP
in the unmount path.
> /*
> + * ioctl_freeze - Freeze the filesystem.
> + *
> + * @filp: target file
> + *
> + * Call freeze_bdev() to freeze the filesystem.
> + */
This is not a kerneldoc comment. But I think it can be simply removed
anyway, as it's a quite trivial function with static scope.
> +/*
> + * ioctl_thaw - Thaw the filesystem.
> + *
> + * @filp: target file
> + *
> + * Call thaw_bdev() to thaw the filesystem.
> + */
Same here.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists