From: Benjamin Coddington <bcodding@redhat.com>
To: stable@vger.kernel.org
Cc: trond.myklebust@hammerspace.com, bcodding@redhat.com,
gregkh@linuxfoundation.org
Subject: Patches for upstream 3f015d89a47c NFS COPY/CLONE - stable versions follow
Date: Mon, 29 Nov 2021 13:41:47 -0500 [thread overview]
Message-ID: <cover.1638210409.git.bcodding@redhat.com> (raw)
The five patches referencing this cover letter are backports of upstream
fix "3f015d89a47c NFSv42: Fix pagecache invalidation after COPY/CLONE",
which did not apply cleanly to longterm trees.
Note: while the upstream fix received extensive testing, these backports
have been build-tested only.
Benjamin Coddington (1):
NFSv42: Fix pagecache invalidation after COPY/CLONE
fs/nfs/nfs42proc.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.31.1
next reply other threads:[~2021-11-29 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 18:41 Benjamin Coddington [this message]
2021-11-29 18:41 ` [stable v4.14 PATCH] NFSv42: Fix pagecache invalidation after COPY/CLONE Benjamin Coddington
2021-11-29 18:41 ` [stable v4.19 " Benjamin Coddington
2021-11-29 18:41 ` [stable v4.9 " Benjamin Coddington
2021-11-29 18:41 ` [stable v5.10 " Benjamin Coddington
2021-11-29 18:41 ` [stable v5.4 " Benjamin Coddington
2021-12-01 9:13 ` Patches for upstream 3f015d89a47c NFS COPY/CLONE - stable versions follow Greg KH
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.1638210409.git.bcodding@redhat.com \
--to=bcodding@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.