* question about tty_port.c
@ 2013-07-05 6:58 gianluca
0 siblings, 0 replies; only message in thread
From: gianluca @ 2013-07-05 6:58 UTC (permalink / raw)
To: linux-serial
Hi,
I was getting kernel panics using an rfcomm bluetooth serial port with the
kernel 3.10 and searching the web I stumbled upon the following issue, which
seems to be exactly the problem I have:
http://marc.info/?t=136868685500006&r=1&w=2
So I went to look tty_port.c to understand the lifetime of the tty_port objects
and fix rfcomm/tty.c
This is unrelated to the issue I have but it seems to me that in
tty_port_tty_hangup we could leak a tty object:
if (tty && (!check_clocal || !C_CLOCAL(tty))) {
tty_hangup(tty);
tty_kref_put(tty);
}
If the first condition is true (tty != NULL) and the second is false we never
call tty_kref_put.
However I could be wrong and in this case I apologize.
I don't understand the inner working of this code, I was just trying to fix
the oops I get, without luck unfortunately.
Ciao,
Gianluca
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-07-05 6:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-05 6:58 question about tty_port.c gianluca
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox