This is a note to let you know that I've just added the patch titled
serial: pch_uart: fix tty-kref leak in rx-error path
to the 3.4-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:
serial-pch_uart-fix-tty-kref-leak-in-rx-error-path.patch
and it can be found in the queue-3.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 73449fe73fa3d46232176fe6c73702b29b6479d2 Mon Sep 17 00:00:00 2001
From: Johan Hovold <jhovold@xxxxxxxxx>
Date: Tue, 10 Sep 2013 12:50:49 +0200
Subject: serial: pch_uart: fix tty-kref leak in rx-error path
From: Johan Hovold <jhovold@xxxxxxxxx>
commit fc0919c68cb2f75bb1af759315f9d7e2a9443c28 upstream.
Fix tty-kref leak introduced by commit 384e301e ("pch_uart: fix a
deadlock when pch_uart as console") which never put its tty reference.
Signed-off-by: Johan Hovold <jhovold@xxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
Cc: Rui Xiang <rui.xiang@xxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/tty/serial/pch_uart.c | 2 ++
1 file changed, 2 insertions(+)
--- a/drivers/tty/serial/pch_uart.c
+++ b/drivers/tty/serial/pch_uart.c
@@ -1065,6 +1065,8 @@ static void pch_uart_err_ir(struct eg20t
if (tty == NULL) {
for (i = 0; error_msg[i] != NULL; i++)
dev_err(&priv->pdev->dev, error_msg[i]);
+ } else {
+ tty_kref_put(tty);
}
}
Patches currently in stable-queue which might be from jhovold@xxxxxxxxx are
queue-3.4/usb-serial-option-add-support-for-novatel-e371-pcie-card.patch
queue-3.4/serial-pch_uart-fix-tty-kref-leak-in-rx-error-path.patch
queue-3.4/usb-ftdi_sio-add-novatech-orionlxm-product-id.patch
queue-3.4/serial-pch_uart-fix-tty-kref-leak-in-dma-rx-path.patch
queue-3.4/usb-io_ti-fix-firmware-download-on-big-endian-machines-part-2.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html