From: Jeff Layton <jlayton@kernel.org>
To: Anna Schumaker <anna@kernel.org>, Trond Myklebust <trondmy@kernel.org>
Cc: Olga Kornievskaia <aglo@umich.edu>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] nfs: delegated attribute fixes
Date: Fri, 13 Mar 2026 14:20:18 -0400 [thread overview]
Message-ID: <3792a08bc04f54c47f34573fa868c2453e3c4415.camel@kernel.org> (raw)
In-Reply-To: <bde355a1-15e2-48dd-a042-1b7cb801f926@app.fastmail.com>
On Fri, 2026-03-13 at 13:48 -0400, Anna Schumaker wrote:
> Hi Jeff,
>
> On Thu, Mar 5, 2026, at 1:53 PM, Jeff Layton wrote:
> > This patchset fixes a couple of test failures in xfstests when delegated
>
> Can you add fixes tags to the patches?
>
>
Sure.
> > timestamps are enabled. Please consider for v7.1!
> >
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > Jeff Layton (2):
> > nfs: fix utimensat() for atime with delegated timestamps
I think this one maybe?
Fixes: 40f45ab3814f ("NFS: Further fixes to attribute delegation a/mtime changes")
> > nfs: update inode ctime after removexattr operation
I'm a little less sure on this one.
Technically, this worked until delegated timestamps were introduced,
but ISTM that omitting the GETATTR in the first place was a mistake:
Fixes: 3e1f02123fba ("NFSv4.2: add client side XDR handling for extended attributes")
>
Can you tack those onto the patches or do you need me to resend?
Thanks,
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2026-03-13 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 18:53 [PATCH 0/2] nfs: delegated attribute fixes Jeff Layton
2026-03-05 18:53 ` [PATCH 1/2] nfs: fix utimensat() for atime with delegated timestamps Jeff Layton
2026-03-05 18:53 ` [PATCH 2/2] nfs: update inode ctime after removexattr operation Jeff Layton
2026-03-13 15:58 ` [PATCH 0/2] nfs: delegated attribute fixes Olga Kornievskaia
2026-03-13 17:48 ` Anna Schumaker
2026-03-13 17:48 ` Anna Schumaker
2026-03-13 18:20 ` Jeff Layton [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=3792a08bc04f54c47f34573fa868c2453e3c4415.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=aglo@umich.edu \
--cc=anna@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox