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, Chris Mason <clm@meta.com>,
	Jeff Layton <jlayton@kernel.org>, Chuck Lever <cel@kernel.org>
Subject: Re: [PATCH 5.10.y] nfsd: release layout stid on setlease failure
Date: Fri,  3 Jul 2026 22:05:06 -0400	[thread overview]
Message-ID: <2026070315-stable-reply-0012@kernel.org> (raw)
In-Reply-To: <20260703033954.1602126-1-cel@kernel.org>

On Thu, Jul 02, 2026 at 11:39:54PM -0400, Chuck Lever wrote:
> From: Chris Mason <clm@meta.com>
>
> commit 30d55c8aabb261bc3f427d6b9aae7ef6206063f9 upstream.

Queued for 5.10.y, thanks!

-- 
Thanks,
Sasha

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2026070228-repeater-synthesis-1c1b@gregkh>
2026-07-03  3:39 ` [PATCH 5.10.y] nfsd: release layout stid on setlease failure 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-0012@kernel.org \
    --to=sashal@kernel.org \
    --cc=cel@kernel.org \
    --cc=clm@meta.com \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --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