The patch titled bluetooth rfcomm: tty_close before destruct has been added to the -mm tree. Its filename is bluetooth-rfcomm-tty_close-before-destruct.patch *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: bluetooth rfcomm: tty_close before destruct From: Dave Young <hidave.darkstar@xxxxxxxxx> rfcomm_dev_del could be called twice time in release function. one by rfcomm_tty_hangup, another by rfcomm_release_dev, this will cause the device being destructed before rfcomm_tty_close. Signed-off-by: Dave Young <hidave.darkstar@xxxxxxxxx> Cc: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> Cc: Marcel Holtmann <marcel@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- net/bluetooth/rfcomm/tty.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff -puN net/bluetooth/rfcomm/tty.c~bluetooth-rfcomm-tty_close-before-destruct net/bluetooth/rfcomm/tty.c --- a/net/bluetooth/rfcomm/tty.c~bluetooth-rfcomm-tty_close-before-destruct +++ a/net/bluetooth/rfcomm/tty.c @@ -424,8 +424,8 @@ static int rfcomm_release_dev(void __use /* Shut down TTY synchronously before freeing rfcomm_dev */ if (dev->tty) tty_vhangup(dev->tty); - - rfcomm_dev_del(dev); + else if (!test_bit(RFCOMM_RELEASE_ONHUP, &dev->flags)) + rfcomm_dev_del(dev); rfcomm_dev_put(dev); return 0; } _ Patches currently in -mm which might be from hidave.darkstar@xxxxxxxxx are gx-suspmodc-use-boot_cpu_data-instead-of-current_cpu_data.patch bluetooth-hidp_process_hid_control-remove-unnecessary-parameter-dealing.patch bluetooth-rfcomm-tty_close-before-destruct.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