From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 OPEN returns a zero cinfo.after on tmpfs
Date: Tue, 4 Jan 2022 11:56:34 -0500 [thread overview]
Message-ID: <20220104165634.GE7815@fieldses.org> (raw)
In-Reply-To: <49640909-A7F0-4004-AF55-859621B26D38@oracle.com>
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.
prev parent reply other threads:[~2022-01-04 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 4:46 NFSv4 OPEN returns a zero cinfo.after on tmpfs Chuck Lever III
2022-01-04 16:56 ` Bruce Fields [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220104165634.GE7815@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.