From: "Anna Schumaker" <anna@kernel.org>
To: "Olga Kornievskaia" <aglo@umich.edu>, "Jeff Layton" <jlayton@kernel.org>
Cc: "Trond Myklebust" <trondmy@kernel.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] nfs: delegated attribute fixes
Date: Fri, 13 Mar 2026 13:48:42 -0400 [thread overview]
Message-ID: <42c59ab6-9de3-4062-b8be-651f7f21400a@app.fastmail.com> (raw)
In-Reply-To: <CAN-5tyHJhwJU=71gxiKJYFnJFGA5xWUg0CQpbJ9=YgqMVi72RQ@mail.gmail.com>
Hi Olga,
On Fri, Mar 13, 2026, at 11:58 AM, Olga Kornievskaia wrote:
> I can confirm that generic/221 and generic/728 no longer fail with
> this patch series applied.
Thanks for checking that. Can we add your "Tested-by" to the commits?
Anna
>
> On Thu, Mar 5, 2026 at 1:53 PM Jeff Layton <jlayton@kernel.org> wrote:
>>
>> This patchset fixes a couple of test failures in xfstests when delegated
>> 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
>> nfs: update inode ctime after removexattr operation
>>
>> fs/nfs/inode.c | 9 +--------
>> fs/nfs/nfs42proc.c | 18 ++++++++++++++++--
>> fs/nfs/nfs42xdr.c | 10 ++++++++--
>> include/linux/nfs_xdr.h | 3 +++
>> 4 files changed, 28 insertions(+), 12 deletions(-)
>> ---
>> base-commit: c107785c7e8dbabd1c18301a1c362544b5786282
>> change-id: 20260305-nfs-7-1-9f71bcde58c5
>>
>> Best regards,
>> --
>> Jeff Layton <jlayton@kernel.org>
>>
next prev parent reply other threads:[~2026-03-13 17:49 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 [this message]
2026-03-13 17:48 ` Anna Schumaker
2026-03-13 18:20 ` Jeff Layton
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=42c59ab6-9de3-4062-b8be-651f7f21400a@app.fastmail.com \
--to=anna@kernel.org \
--cc=aglo@umich.edu \
--cc=jlayton@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