summaryrefslogtreecommitdiff
path: root/sound/hda/ext
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@redhat.com>2021-03-08 18:52:29 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-03-20 12:43:44 +0300
commitdf8596f5774387f92133e0e5b7e05808ff6595d7 (patch)
tree743fcffbe795cb1206c63414001fb9b7c68c217b /sound/hda/ext
parent894ecf0cb505561b9f37b302b7479eea939b0790 (diff)
downloadlinux-df8596f5774387f92133e0e5b7e05808ff6595d7.tar.xz
Revert "nfsd4: a client's own opens needn't prevent delegations"
commit 6ee65a773096ab3f39d9b00311ac983be5bdeb7c upstream. This reverts commit 94415b06eb8aed13481646026dc995f04a3a534a. That commit claimed to allow a client to get a read delegation when it was the only writer. Actually it allowed a client to get a read delegation when *any* client has a write open! The main problem is that it's depending on nfs4_clnt_odstate structures that are actually only maintained for pnfs exports. This causes clients to miss writes performed by other clients, even when there have been intervening closes and opens, violating close-to-open cache consistency. We can do this a different way, but first we should just revert this. I've added pynfs 4.1 test DELEG19 to test for this, as I should have done originally! Cc: stable@vger.kernel.org Reported-by: Timo Rothenpieler <timo@rothenpieler.org> Signed-off-by: J. Bruce Fields <bfields@redhat.com> Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'sound/hda/ext')
0 files changed, 0 insertions, 0 deletions