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

    gpio: sysfs: fix memory leak in gpiod_export_link

to the 3.18-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:
     gpio-sysfs-fix-memory-leak-in-gpiod_export_link.patch
and it can be found in the queue-3.18 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From 0f303db08df0df9bd0966443ad6001e63960af16 Mon Sep 17 00:00:00 2001
From: Johan Hovold <[email protected]>
Date: Mon, 26 Jan 2015 12:02:45 +0100
Subject: gpio: sysfs: fix memory leak in gpiod_export_link

From: Johan Hovold <[email protected]>

commit 0f303db08df0df9bd0966443ad6001e63960af16 upstream.

Fix memory leak in the gpio sysfs interface due to failure to drop
reference to device returned by class_find_device when creating a link.

Fixes: a4177ee7f1a8 ("gpiolib: allow exported GPIO nodes to be named using 
sysfs links")
Signed-off-by: Johan Hovold <[email protected]>
Signed-off-by: Linus Walleij <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 drivers/gpio/gpiolib-sysfs.c |    1 +
 1 file changed, 1 insertion(+)

--- a/drivers/gpio/gpiolib-sysfs.c
+++ b/drivers/gpio/gpiolib-sysfs.c
@@ -630,6 +630,7 @@ int gpiod_export_link(struct device *dev
                if (tdev != NULL) {
                        status = sysfs_create_link(&dev->kobj, &tdev->kobj,
                                                name);
+                       put_device(tdev);
                } else {
                        status = -ENODEV;
                }


Patches currently in stable-queue which might be from [email protected] are

queue-3.18/gpio-sysfs-fix-memory-leak-in-gpiod_sysfs_set_active_low.patch
queue-3.18/gpio-sysfs-fix-memory-leak-in-gpiod_export_link.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to