On Fri, 26 Oct 2012 10:11:45 +0200 Guillaume Juan <guillaume.juan@xxxxxxxxxxxx> wrote: > From: Guillaume Juan <guillaume.juan@xxxxxxxxxxxx> > > If gsm->tty happens to be NULL in gsmld_output, avoid crashing the kernel (the crash is replaced by a warning dump). More important is fixing the bug completely. I agree there is a bug I don't think your fix is sufficient however. You no longer set dlci->dead before doing the dlci release so what stops a SABM from the other end racing this ? Also moving the gsm_dlci_release seems to have no value at all because there is no locking in the code concerned so viewed from any other thread you've changed nothing but timings. Yes its probably way harder to hit. I can see two ways of tackling it both of which basically come down to the same thing. In gsmld_detach_gsm after the gsm_cleanup_mux we need to - be sure the thing cannot re-open - wait until all the DLCIs are dead then do the tty_kref_put and gsm->tty = NULL Thoughts ? Alan -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
