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

    Connector: Correctly set the error code in case of success

to the 2.6.39-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:
     connector-correctly-set-the-error-code-in-case-of-success.patch
and it can be found in the queue-2.6.39 subdirectory.

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


>From 663dd6dcaf7e95526e469e91f41972a9c0cca30c Mon Sep 17 00:00:00 2001
From: "K. Y. Srinivasan" <k...@microsoft.com>
Date: Tue, 17 May 2011 15:25:38 -0700
Subject: Connector: Correctly set the error code in case of success
 when dispatching receive callbacks

From: "K. Y. Srinivasan" <k...@microsoft.com>

commit 663dd6dcaf7e95526e469e91f41972a9c0cca30c upstream.

The recent changes to the connector code introduced this bug where even
when a callback was invoked, we would return an error resulting in
double freeing of the skb. This patch fixes this bug.

Signed-off-by: K. Y. Srinivasan <k...@microsoft.com>
Acked-by: Evgeniy Polyakov <z...@ioremap.net>
Signed-off-by: Greg Kroah-Hartman <gre...@suse.de>

---
 drivers/connector/connector.c |    1 +
 1 file changed, 1 insertion(+)

--- a/drivers/connector/connector.c
+++ b/drivers/connector/connector.c
@@ -139,6 +139,7 @@ static int cn_call_callback(struct sk_bu
        spin_unlock_bh(&dev->cbdev->queue_lock);
 
        if (cbq != NULL) {
+               err = 0;
                cbq->callback(msg, nsp);
                kfree_skb(skb);
                cn_queue_release_callback(cbq);


Patches currently in stable-queue which might be from k...@microsoft.com are

queue-2.6.39/connector-correctly-set-the-error-code-in-case-of-success.patch
queue-2.6.39/connector-set-the-cn_netlink_users-correctly.patch

_______________________________________________
stable mailing list
stable@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/stable

Reply via email to