[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[dm-devel] Re: [RFC PATCH 1/3] Implement generic freeze feature
- From: Andreas Dilger <adilger sun com>
- To: Takashi Sato <t-sato yk jp nec com>
- Cc: "linux-fsdevel vger kernel org" <linux-fsdevel vger kernel org>, "dm-devel redhat com" <dm-devel redhat com>, "linux-ext4 vger kernel org" <linux-ext4 vger kernel org>, "linux-kernel vger kernel org" <linux-kernel vger kernel org>, "xfs oss sgi com" <xfs oss sgi com>
- Subject: [dm-devel] Re: [RFC PATCH 1/3] Implement generic freeze feature
- Date: Mon, 19 May 2008 21:57:12 -0600
On May 14, 2008 17:06 +0900, Takashi Sato wrote:
> +static int ioctl_freeze(struct file *filp)
> +{
> + struct super_block *sb = filp->f_path.dentry->d_inode->i_sb;
> +
> + if (!capable(CAP_SYS_ADMIN))
> + return -EPERM;
> +
> + /* If filesystem doesn't support freeze feature, return. */
> + if (sb->s_op->write_super_lockfs == NULL)
> + return -EINVAL;
Should this be EINVAL, or EOPNOTSUPP? Usually EINVAL means there is
something wrong with the passed ioctl parameters (e.g. bad value),
while EOPNOTSUPP is "operation not supported" and makes more sense.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]