Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/ https://git.shady.money/linux/atom?h=v3.9 2013-03-28T15:50:22Z 2013-03-28T15:50:22Z Konstantin Holoborodko klh.kernel@gmail.com 2013-03-28T15:06:13Z urn:sha1:482b0b5d82bd916cc0c55a2abf65bdc69023b843 It enhances the driver for FTDI-based USB serial adapters to recognize Mitsubishi Electric Corp. USB/RS422 Converters as FT232BM chips and support them. https://search.meau.com/?q=FX-USB-AW Signed-off-by: Konstantin Holoborodko <klh.kernel@gmail.com> Tested-by: Konstantin Holoborodko <klh.kernel@gmail.com> Cc: stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-03-26T16:28:29Z Ming Lei tom.leiming@gmail.com 2013-03-26T02:49:55Z urn:sha1:eba0e3c3a0ba7b96f01cbe997680f6a4401a0bfc Johan's 'fix use-after-free in TIOCMIWAIT' patchset[1] introduces one bug which can cause kernel hang when opening port. This patch initialized the 'port->delta_msr_wait' waitqueue head to fix the bug which is introduced in 3.9-rc4. [1], http://marc.info/?l=linux-usb&m=136368139627876&w=2 Cc: stable <stable@vger.kernel.org> Signed-off-by: Ming Lei <tom.leiming@gmail.com> Acked-by: Johan Hovold <jhovold@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-03-21T22:59:05Z Johan Hovold jhovold@gmail.com 2013-03-19T08:21:26Z urn:sha1:fc98ab873aa3dbe783ce56a2ffdbbe7c7609521a Use the port wait queue and make sure to check the serial disconnected flag before accessing private port data after waking up. This is is needed as the private port data (including the wait queue itself) can be gone when waking up after a disconnect. Cc: stable <stable@vger.kernel.org> Signed-off-by: Johan Hovold <jhovold@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-03-21T22:59:05Z Johan Hovold jhovold@gmail.com 2013-03-19T08:21:25Z urn:sha1:43a66b4c417ad15f6d2f632ce67ad195bdf999e8 Use the port wait queue and make sure to check the serial disconnected flag before accessing private port data after waking up. This is is needed as the private port data (including the wait queue itself) can be gone when waking up after a disconnect. Cc: stable <stable@vger.kernel.org> Signed-off-by: Johan Hovold <jhovold@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-03-21T22:59:05Z Johan Hovold jhovold@gmail.com 2013-03-19T08:21:24Z urn:sha1:dbcea7615d8d7d58f6ff49d2c5568113f70effe9 Use the port wait queue and make sure to check the serial disconnected flag before accessing private port data after waking up. This is is needed as the private port data (including the wait queue itself) can be gone when waking up after a disconnect. Cc: stable <stable@vger.kernel.org> Signed-off-by: Johan Hovold <jhovold@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-03-21T22:59:05Z Johan Hovold jhovold@gmail.com 2013-03-19T08:21:23Z urn:sha1:69f87f40d2b98e8b4ab82a121fd2bd584690b887 Use the port wait queue and make sure to check the serial disconnected flag before accessing private port data after waking up. This is is needed as the private port data (including the wait queue itself) can be gone when waking up after a disconnect. Cc: stable <stable@vger.kernel.org> Signed-off-by: Johan Hovold <jhovold@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-03-21T22:59:05Z Johan Hovold jhovold@gmail.com 2013-03-19T08:21:22Z urn:sha1:40509ca982c00c4b70fc00be887509feca0bff15 Use the port wait queue and make sure to check the serial disconnected flag before accessing private port data after waking up. This is is needed as the private port data (including the wait queue itself) can be gone when waking up after a disconnect. Cc: stable <stable@vger.kernel.org> Signed-off-by: Johan Hovold <jhovold@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-03-21T22:59:04Z Johan Hovold jhovold@gmail.com 2013-03-19T08:21:21Z urn:sha1:8edfdab37157d2683e51b8be5d3d5697f66a9f7b Use the port wait queue and make sure to check the serial disconnected flag before accessing private port data after waking up. This is is needed as the private port data (including the wait queue itself) can be gone when waking up after a disconnect. Cc: stable <stable@vger.kernel.org> Signed-off-by: Johan Hovold <jhovold@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-03-21T22:59:04Z Johan Hovold jhovold@gmail.com 2013-03-19T08:21:20Z urn:sha1:a14430db686b8e459e1cf070a6ecf391515c9ab9 Use the port wait queue and make sure to check the serial disconnected flag before accessing private port data after waking up. This is is needed as the private port data (including the wait queue itself) can be gone when waking up after a disconnect. Cc: stable <stable@vger.kernel.org> Signed-off-by: Johan Hovold <jhovold@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-03-21T22:59:04Z Johan Hovold jhovold@gmail.com 2013-03-19T08:21:19Z urn:sha1:e670c6af12517d08a403487b1122eecf506021cf Make sure waiting processes are woken on modem-status changes. Currently processes are only woken on termios changes regardless of whether the modem status has changed. Cc: stable <stable@vger.kernel.org> Signed-off-by: Johan Hovold <jhovold@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>