summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorTrond Myklebust <trondmy@gmail.com>2018-09-05 14:07:14 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-09-26 08:39:34 +0200
commit8bfbd71c11462058c1203a289e7be568273bc8af (patch)
tree6fde77a8b7a0658ff617df981fb22a678040998e /security
parenta12ad4f33e6ff93fb16b7c432a68d53f10b27b02 (diff)
downloadlinux-stable-8bfbd71c11462058c1203a289e7be568273bc8af.tar.gz
linux-stable-8bfbd71c11462058c1203a289e7be568273bc8af.tar.bz2
linux-stable-8bfbd71c11462058c1203a289e7be568273bc8af.zip
NFSv4.1 fix infinite loop on I/O.
commit 994b15b983a72e1148a173b61e5b279219bb45ae upstream. The previous fix broke recovery of delegated stateids because it assumes that if we did not mark the delegation as suspect, then the delegation has effectively been revoked, and so it removes that delegation irrespectively of whether or not it is valid and still in use. While this is "mostly harmless" for ordinary I/O, we've seen pNFS fail with LAYOUTGET spinning in an infinite loop while complaining that we're using an invalid stateid (in this case the all-zero stateid). What we rather want to do here is ensure that the delegation is always correctly marked as needing testing when that is the case. So we want to close the loophole offered by nfs4_schedule_stateid_recovery(), which marks the state as needing to be reclaimed, but not the delegation that may be backing it. Fixes: 0e3d3e5df07dc ("NFSv4.1 fix infinite loop on IO BAD_STATEID error") Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com> Cc: stable@vger.kernel.org # v4.11+ Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions