Linux NFS development
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	linux-nfs@vger.kernel.org, Scott Mayhew <smayhew@redhat.com>,
	Chuck Lever <cel@kernel.org>
Subject: Re: [PATCH 6.12.y 1/2] nfsd: fix file change detection in CB_GETATTR
Date: Fri,  3 Jul 2026 22:05:01 -0400	[thread overview]
Message-ID: <2026070315-stable-reply-0007@kernel.org> (raw)
In-Reply-To: <20260702202749.1618630-1-cel@kernel.org>

On Thu, Jul 02, 2026 at 04:27:48PM -0400, Chuck Lever wrote:
> commit 304d81a2fbf2b454def4debcb38ea173911b72cd upstream.

Queued the series for 6.12.y, with the author of 2/2 fixed up to Chris
Mason per your follow-up. Thanks!

-- 
Thanks,
Sasha

      parent reply	other threads:[~2026-07-04  2:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 20:27 [PATCH 6.12.y 1/2] nfsd: fix file change detection in CB_GETATTR Chuck Lever
2026-07-02 20:27 ` [PATCH 6.12.y 2/2] nfsd: release layout stid on setlease failure Chuck Lever
2026-07-02 20:45   ` Chuck Lever
2026-07-04  2:05 ` Sasha Levin [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=2026070315-stable-reply-0007@kernel.org \
    --to=sashal@kernel.org \
    --cc=cel@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=smayhew@redhat.com \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox