From: Anna Schumaker <Anna.Schumaker@Netapp.com>
To: <stable@vger.kernel.org>
Subject: Please consider 3be0f80b5f for stable (v4.11+)
Date: Mon, 18 Jun 2018 13:29:44 -0400 [thread overview]
Message-ID: <d9966949-a3ca-aab5-fd01-2f5f0bbef86d@Netapp.com> (raw)
Hi Stable folks,
Please consider adding:
commit 3be0f80b5fe9c16eca2d538f799b94ca8aa59433
Author: Trond Myklebust <trond.myklebust@primarydata.com>
Date: Thu Oct 19 15:46:45 2017 -0400
NFSv4.1: Fix up replays of interrupted requests
This patch fixes a data corruption issue that happens if the interrupted slot is reused by the same type of NFS operation (such as two different WRITE requests). I should apply cleanly to v4.11+
Thanks,
Anna
next reply other threads:[~2018-06-18 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 17:29 Anna Schumaker [this message]
2018-06-21 21:12 ` Please consider 3be0f80b5f for stable (v4.11+) 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=d9966949-a3ca-aab5-fd01-2f5f0bbef86d@Netapp.com \
--to=anna.schumaker@netapp.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;
as well as URLs for NNTP newsgroup(s).