Hi there, On Sat, Dec 17, 2011 at 10:55, Thilo-Alexander Ginkel <thilo@xxxxxxxxxx> wrote: > There is a race condition involving acm_tty_hangup() and acm_tty_close() where > hangup() would attempt to access tty->driver_data without proper locking and > NULL checking after close() has potentially already set it to NULL. > One possibility to (sporadically) trigger this behavior is to perform a > suspend/resume cycle with a running WWAN data connection. > > This patch addresses the issue by introducing a NULL check for > tty->driver_data in acm_tty_hangup() protected by open_mutex and exiting > gracefully when hangup() is invoked on a device that has already been closed. just wondering: Is there any chance that this patch will make it into 3.3? I would really appreciate that as the bug it fixes is pretty annoying (and potentially causes data loss when the laptop locks up on resume) and I am sure that I am not the only one affected by it (at least all Lenovo T420s with an Ericsson F5521gw WWAN modem should be similarly affected). If you would like to see any changes to the code or commit message before considering the patch for inclusion, please let me know. Thanks, Thilo -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
