linux-kernel - Re: [PATCH v2] serial_core: fix uart PORT

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] [day] [month] [year] [list]

Message-ID: <20140423133454.402af61e@alan.etchedpixels.co.uk>
Date:	Wed, 23 Apr 2014 13:34:54 +0100
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Thomas Pfaff <tpfaff@....com>
Cc:	<gregkh@...uxfoundation.org>, <jslaby@...e.cz>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] serial_core: fix uart PORT_UNKNOWN handling

On Wed, 23 Apr 2014 12:33:22 +0200
Thomas Pfaff <tpfaff@....com> wrote:

> From: "Thomas Pfaff" <tpfaff@....com>
> 
> While porting a RS485 driver from 2.6.29 to 3.14, i noticed that the serial tty 
> driver could break it by using uart ports that it does not own :
> 
> 1. uart_change_pm ist called during uart_open and calls the uart pm function
>    without checking for PORT_UNKNOWN.
>    The fix is to move uart_change_pm from uart_open to uart_port_startup.
> 2. The return code from the uart request_port call in uart_set_info is not
>    handled properly, leading to the situation that the serial driver also
>    thinks it owns the uart ports.
>    This can triggered by doing following actions :
> 
>    setserial /dev/ttyS0 uart none    # release the uart ports
>    modprobe lirc-serial              # or any other device that uses the uart
>    setserial /dev/ttyS0 uart 16550   # gives no error and the uart tty driver
>                                      # can use the ports as well
> 
> Signed-off-by: Thomas Pfaff <tpfaff@....com>
Reviewed-by: Alan Cox <alan@...ux.intel.com>
--
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/