bluetooth rfcomm tty: destroy before tty_close()

rfcomm dev could be deleted in tty_hangup, so we must not call
rfcomm_dev_del again to prevent from destroying rfcomm dev before tty
close.

Signed-off-by: Dave Young <hidave.darkstar@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

authored by Dave Young and committed by David S. Miller 93d80740 6e46c8cb

+2 -1
+2 -1
net/bluetooth/rfcomm/tty.c
··· 429 if (dev->tty) 430 tty_vhangup(dev->tty); 431 432 - rfcomm_dev_del(dev); 433 rfcomm_dev_put(dev); 434 return 0; 435 }
··· 429 if (dev->tty) 430 tty_vhangup(dev->tty); 431 432 + if (!test_bit(RFCOMM_RELEASE_ONHUP, &dev->flags)) 433 + rfcomm_dev_del(dev); 434 rfcomm_dev_put(dev); 435 return 0; 436 }