The patch titled
rfcomm: hangup ttys before releasing rfcomm_dev
has been removed from the -mm tree. Its filename was
rfcomm-hangup-ttys-before-releasing-rfcomm_dev.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: rfcomm: hangup ttys before releasing rfcomm_dev
Addresses the oops at http://bugzilla.kernel.org/show_bug.cgi?id=7509
The core problem is that rfcomm socket layer ioctl can release rfcomm_dev
struct while rfcomm tty layer is still actively using it. Calling tty_vhangup
is needed for a synchronous hangup before rfcomm_dev is freed.
Cc: Marcel Holtmann <marcel@xxxxxxxxxxxx>
Acked-by: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Cc: <stable@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
net/bluetooth/rfcomm/tty.c | 6 ++++++
1 file changed, 6 insertions(+)
diff -puN net/bluetooth/rfcomm/tty.c~rfcomm-hangup-ttys-before-releasing-rfcomm_dev net/bluetooth/rfcomm/tty.c
--- a/net/bluetooth/rfcomm/tty.c~rfcomm-hangup-ttys-before-releasing-rfcomm_dev
+++ a/net/bluetooth/rfcomm/tty.c
@@ -399,6 +399,12 @@ static int rfcomm_release_dev(void __use
if (dev->tty)
tty_vhangup(dev->tty);
+ /*
+ * Be nice and shut down tty(s) synchronously before freeing rfcomm_dev
+ */
+ if (dev->tty)
+ tty_vhangup(dev->tty);
+
rfcomm_dev_del(dev);
rfcomm_dev_put(dev);
return 0;
_
Patches currently in -mm which might be from marcel@xxxxxxxxxxxx are
origin.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
