Commit a4813799 authored by Adam McCoy's avatar Adam McCoy Committed by Steve French

cifs: fix leaked reference on requeued write

Failed async writes that are requeued may not clean up a refcount
on the file, which can result in a leaked open. This scenario arises
very reliably when using persistent handles and a reconnect occurs
while writing.

cifs_writev_requeue only releases the reference if the write fails
(rc != 0). The server->ops->async_writev operation will take its own
reference, so the initial reference can always be released.
Signed-off-by: default avatarAdam McCoy <adam@forsedomani.com>
Signed-off-by: default avatarSteve French <stfrench@microsoft.com>
CC: Stable <stable@vger.kernel.org>
Reviewed-by: default avatarPavel Shilovsky <pshilov@microsoft.com>
parent 9bd21d4b
...@@ -2152,8 +2152,8 @@ cifs_writev_requeue(struct cifs_writedata *wdata) ...@@ -2152,8 +2152,8 @@ cifs_writev_requeue(struct cifs_writedata *wdata)
} }
} }
if (rc) {
kref_put(&wdata2->refcount, cifs_writedata_release); kref_put(&wdata2->refcount, cifs_writedata_release);
if (rc) {
if (is_retryable_error(rc)) if (is_retryable_error(rc))
continue; continue;
i += nr_pages; i += nr_pages;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment