linux-kernel - Re: post 3.14 serial regression

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: <53456EF8.8060805@sr71.net>
Date:	Wed, 09 Apr 2014 09:02:00 -0700
From:	Dave Hansen <dave@...1.net>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Dave Hansen <dave.hansen@...el.com>
CC:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Geert Uytterhoeven <geert+renesas@...ux-m68k.org>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-serial@...r.kernel.org, jslaby@...e.cz
Subject: Re: post 3.14 serial regression

On 04/08/2014 05:36 PM, Greg Kroah-Hartman wrote:
>> > Looks like this just changed the detection order so my device went from
>> > ttyS2 to ttyS4:
>> > 
>> > # cat /proc/tty/driver/serial
>> > serinfo:1.0 driver revision:
>> > 0: uart:16550A port:000003F8 irq:4 tx:0 rx:0 CTS|DSR|CD
>> > 1: uart:16550A port:000002F8 irq:3 tx:0 rx:0
>> > 2: uart:unknown port:000003E8 irq:4
>> > 3: uart:unknown port:000002E8 irq:3
>> > 4: uart:ST16650V2 port:00001008 irq:18 tx:0 rx:0
>> > 5: uart:ST16650V2 port:00001000 irq:19 tx:0 rx:0
> That's not good.
> 
> Geert, any idea how to fix this?  Or should I just revert your change to
> get back to the "working" behavior?

During some large bisects on previous kernels, I've noticed it make a
switch from ttyS2->ttyS4 before.  In other words, this might have
restored some *old* behavior inadvertently.

The annoying thing is that these assignments *do* keep swapping around.
 I don't really care whether or not we revert this, only that we pick
one order and stick with it.

--
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/