Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@kernel.org>
To: stable@vger.kernel.org
Subject: [PATCH 5.15.y 0/2] FAILED: patch "[PATCH] NFS: Fix a race when updating an existing write" failed to apply to 5.15-stable tree
Date: Thu, 28 Aug 2025 10:35:15 -0700	[thread overview]
Message-ID: <cover.1756402339.git.trond.myklebust@hammerspace.com> (raw)
In-Reply-To: <2025082225-cling-drainer-d884@gregkh>

From: Trond Myklebust <trond.myklebust@hammerspace.com>

The patch in question has a dependency on a previous patch by Christoph.
Both needed backporting to Linux 5.15.y

Christoph Hellwig (1):
  nfs: fold nfs_page_group_lock_subrequests into
    nfs_lock_and_join_requests

Trond Myklebust (1):
  NFS: Fix a race when updating an existing write

 fs/nfs/pagelist.c        |  86 ++----------------------
 fs/nfs/write.c           | 140 +++++++++++++++++++++++++--------------
 include/linux/nfs_page.h |   2 +-
 3 files changed, 97 insertions(+), 131 deletions(-)

-- 
2.51.0


WARNING: multiple messages have this Message-ID (diff)
From: Trond Myklebust <trondmy@kernel.org>
To: stable@vger.kernel.org
Subject: [PATCH 5.15.y 0/2] FAILED: patch "[PATCH] NFS: Fix a race when updating an existing write" failed to apply to 5.15-stable tree
Date: Thu, 28 Aug 2025 10:41:11 -0700	[thread overview]
Message-ID: <cover.1756402339.git.trond.myklebust@hammerspace.com> (raw)
Message-ID: <20250828174111.Ms2DYINFE4rWoaoLsmt88qleH5faM-9w3LP-zGxJ8fI@z> (raw)
In-Reply-To: <2025082225-cling-drainer-d884@gregkh>

From: Trond Myklebust <trond.myklebust@hammerspace.com>

The patch in question has a dependency on a previous patch by Christoph.
Both needed backporting to Linux 5.15.y

Christoph Hellwig (1):
  nfs: fold nfs_page_group_lock_subrequests into
    nfs_lock_and_join_requests

Trond Myklebust (1):
  NFS: Fix a race when updating an existing write

 fs/nfs/pagelist.c        |  86 ++----------------------
 fs/nfs/write.c           | 140 +++++++++++++++++++++++++--------------
 include/linux/nfs_page.h |   2 +-
 3 files changed, 97 insertions(+), 131 deletions(-)

-- 
2.51.0


  reply	other threads:[~2025-08-28 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22 14:43 FAILED: patch "[PATCH] NFS: Fix a race when updating an existing write" failed to apply to 5.15-stable tree gregkh
2025-08-28 17:35 ` Trond Myklebust [this message]
2025-08-28 17:35   ` [PATCH 5.15.y 1/2] nfs: fold nfs_page_group_lock_subrequests into nfs_lock_and_join_requests Trond Myklebust
2025-08-28 17:41     ` Trond Myklebust
2025-08-28 17:35   ` [PATCH 5.15.y 2/2] NFS: Fix a race when updating an existing write Trond Myklebust
2025-08-28 17:41     ` Trond Myklebust
2025-08-28 17:41   ` [PATCH 5.15.y 0/2] FAILED: patch "[PATCH] NFS: Fix a race when updating an existing write" failed to apply to 5.15-stable tree Trond Myklebust

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=cover.1756402339.git.trond.myklebust@hammerspace.com \
    --to=trondmy@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