diff options
| author | Johan Hovold <jhovold@gmail.com> | 2013-02-13 17:53:28 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-02-28 06:58:59 -0800 |
| commit | 906c9c42101742d1ec86ab22eb55d24d496830a7 (patch) | |
| tree | f0f61878a686f7cddbfc483f57cf8e244eb5aa1b /net | |
| parent | 46605dae03a55a70d7fd9886f466b435afc7738b (diff) | |
| download | lwn-906c9c42101742d1ec86ab22eb55d24d496830a7.tar.gz lwn-906c9c42101742d1ec86ab22eb55d24d496830a7.zip | |
USB: serial: fix null-pointer dereferences on disconnect
commit b2ca699076573c94fee9a73cb0d8645383b602a0 upstream.
Make sure serial-driver dtr_rts is called with disc_mutex held after
checking the disconnected flag.
Due to a bug in the tty layer, dtr_rts may get called after a device has
been disconnected and the tty-device unregistered. Some drivers have had
individual checks for disconnect to make sure the disconnected interface
was not accessed, but this should really be handled in usb-serial core
(at least until the long-standing tty-bug has been fixed).
Note that the problem has been made more acute with commit 0998d0631001
("device-core: Ensure drvdata = NULL when no driver is bound") as the
port data is now also NULL when dtr_rts is called resulting in further
oopses.
Reported-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>
Signed-off-by: Johan Hovold <jhovold@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions