linux-kernel - Re: usb serial: pl2303 driver TxD "break" stays after close() bug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACMCwJKsr5R2N6zK-+fKEwHLf6xM6q+ni3dAEm3jz+LkE6rM3w@mail.gmail.com>
Date:	Thu, 19 Feb 2015 15:38:39 +0200
From:	Jari Ruusu <jariruusu@...rs.sourceforge.net>
To:	Johan Hovold <johan@...nel.org>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: usb serial: pl2303 driver TxD "break" stays after close() bug

On 2/19/15, Johan Hovold <johan@...nel.org> wrote:
> What happens when you reopen the port? Is the break state cleared then?

Stuck "break" signal is not cleared on re-open.

To clear it, you need to poke it with ioctl(fd, TIOCCBRK, 0)
or disconnect the device.

-- 
Jari Ruusu  4096R/8132F189 12D6 4C3A DCDA 0AA4 27BD  ACDF F073 3C80 8132 F189
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/