Re: [PATCH] NFSD: Implement FATTR4_CLONE_BLKSIZE attribute

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

 



On Sun, Apr 27, 2025 at 12:39:14PM -0400, cel@xxxxxxxxxx wrote:
> NFSD can return 0 here, as at least one client implementation we
> are aware of (the Linux NFS client) treats 0 as meaning "CLONE has
> no alignment restrictions".

Usuaully clone does have a restriction, though.

> Meanwhile we need to consult the nfsv4 Working Group to clarify the
> meaning and use of the value of this attribute.

Yeah, the attribute seems to be severly underspecified, i.e. it does
not even provide a unit that the value is in.

I think the only sane way out is an errate that makes 0 mean
"not specified" and then provides the byte unit and maybe some
other quirks.

> +	/* Linux filesystems have no clone alignment restrictions */

That is absolutely untrue as said above.





[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux