This is a note to let you know that I've just added the patch titled

    CIFS: Fix a memory leak when a lease break comes

to the 3.11-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     cifs-fix-a-memory-leak-when-a-lease-break-comes.patch
and it can be found in the queue-3.11 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.


>From 1a05096de82f3cd672c76389f63964952678506f Mon Sep 17 00:00:00 2001
From: Pavel Shilovsky <pshilov...@samba.org>
Date: Thu, 5 Sep 2013 15:04:04 +0400
Subject: CIFS: Fix a memory leak when a lease break comes

From: Pavel Shilovsky <pshilov...@samba.org>

commit 1a05096de82f3cd672c76389f63964952678506f upstream.

This happens when we receive a lease break from a server, then
find an appropriate lease key in opened files and schedule the
oplock_break slow work. lw pointer isn't freed in this case.

Signed-off-by: Pavel Shilovsky <pshilov...@samba.org>
Signed-off-by: Steve French <smfre...@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>

---
 fs/cifs/smb2misc.c |    1 +
 1 file changed, 1 insertion(+)

--- a/fs/cifs/smb2misc.c
+++ b/fs/cifs/smb2misc.c
@@ -473,6 +473,7 @@ smb2_is_valid_lease_break(char *buffer,
 
                                queue_work(cifsiod_wq, &cfile->oplock_break);
 
+                               kfree(lw);
                                spin_unlock(&cifs_file_list_lock);
                                spin_unlock(&cifs_tcp_ses_lock);
                                return true;


Patches currently in stable-queue which might be from pshilov...@samba.org are

queue-3.11/cifs-fix-a-memory-leak-when-a-lease-break-comes.patch
queue-3.11/cifs-fix-missing-lease-break.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to