Re: [PATCH v10 08/41] btrfs: disallow NODATACOW in ZONED mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Nov 20, 2020 at 12:17:21PM +0800, Anand Jain wrote:
> On 10/11/20 7:26 pm, Naohiro Aota wrote:
> > +				    unsigned int flags)
> > +{
> > +	if (btrfs_is_zoned(fs_info) && (flags & FS_NOCOW_FL))
> 
> 
> > +		return -EPERM;
> 
> nit:
>   Should it be -EINVAL instead? I am not sure. May be David can fix 
> while integrating.

IIRC we've discussed that in some previous iteration. EPERM should be
interpreted as that it's not permitted right now, but otherwise it is a
valid operation/flag. The constraint is the zoned device.

As an example: deleting default subvolume is not permitted (EPERM), but
otherwise subvolume deletion is a valid operation.

So, EINVAL is for invalid combination of parameters or a request for
something that does not make sense at all.



[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux