Hi Gianluca,
On 09/07/13 18:05, Gianluca Anzolin wrote:
In net/bluetooth/rfcomm/tty.c the struct tty is used without proper
refcounting. This leads to OOPS and panics triggered by the tty layer functions
which are invoked after the struct tty has already been destroyed.
This happens for example when the bluetooth connection is lost because the host
goes down unexpectedly.
The fix uses the tty_port_* helpers already in place.
This patch depends on patch "Fix refcount leak in tty_port.c" already sent to
linux-kernel. [0]
Signed-off-by: Gianluca Anzolin <gianluca@xxxxxxxxxxxxxx>
[0] http://lkml.indiana.edu/hypermail/linux/kernel/1307.1/00600.html
Do you have any backtraces of the OOPS and panics ?
In which kernel did you discover the failure ?
What platform were you using, I mean x86, ARM or something else ?
Is this failure easy to reproduce ?
Did you use Bluez userland to control Bluetooth ?
In the failure case, what protocol or application was bound to the
RFCOMM TTY ? I mean was it SLIP, minicom or something else ?
Thanks,
Regards,
Dean Jenkins
Mentor Graphics
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
