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: <20120103160655.69107c93@pyramind.ukuu.org.uk>
Date:	Tue, 3 Jan 2012 16:06:55 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Dave Jones <davej@...hat.com>
Cc:	Jiri Slaby <jslaby@...e.cz>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: serial ports now asserting DTR and RTS during boot; breaks
 connected hardware

On Tue, 3 Jan 2012 10:37:07 -0500
Dave Jones <davej@...hat.com> wrote:

> Jiri,
> We got this report from a user who notes a change in behaviour for
> his serial hardware over the last few kernel versions.
>  
> https://bugzilla.redhat.com/show_bug.cgi?id=771010
> 
> This sounds like it might be related to your DTR/RTS changes back in March 2011 maybe ? 

Looks like your userspace to me at first glance.

ftdi_sio sets up the modem lines in set_termios. Set_termios is called
from ftdi_open. ftdi_open is triggered by userspace.

>  > The following code in the ftdi_sio driver is one suspect but this behavior
>  > happens on 8250 UARTs also so it is systemic now,

Likewise 8250 sets up the lines in serial8250_startup. This is called via
uart_startup which is called via open.

I think a necessary first step would be to test a current kernel on FC14,
or boot a sane simple kernel and test image and see what that does so all
the udev and system startup stuff can be eliminated. Wouldn't surprise me
at all however if something like udev triggered poking around for UPS
devices or 3G modems wasn't the trigger ?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ