Re: NFSv4 OPEN returns a zero cinfo.after on tmpfs

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

 



On Fri, Dec 24, 2021 at 04:46:26AM +0000, Chuck Lever III wrote:
> During some testing I noticed that OPEN frequently returns a
> zero in the cinfo.after field on my test share, which is tmpfs.
> Does not seem to be an issue for xfs.

Thanks for catching this.

> An easy way to address this would be to revert 428a23d2bf0c. But I
> wonder if there are any particular regression tests in the pynfs
> suite that could detect this kind of misbehavior, in case someone
> would like to try to re-implement the optimization in 428a23d2bf0c.

>From a quick grep the only tests I see checking cinfo are in
nfs4.0/servertests/st_rename.py

--b.



[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