linux-kernel - Re: Linux 2.6.x - Serial port signalling not maintained when closing device

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]

Date:	Thu, 26 Mar 2009 08:14:31 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Paul Rolland <rol@...917.net>
Cc:	linux-kernel@...r.kernel.org, rol@...917.net
Subject: Re: Linux 2.6.x - Serial port signalling not maintained when
 closing device

> As far as I can see, I need to have an application that keeps /dev/ttyS0
> open for this to work. As soon as no application is using the port,
> everything goes down again.

Yes - the 2.6 kernel has the newer uart driver layer and is also
(throughout) much more aggressive about power management. You'll see the
same with magic electronic project parallel port hacks where the port is
turned off when the device file is not open.

> This is a significant change between 2.4.x and 2.6.x.

Only to your rather unusual use of things. For normal use the current
behaviour is far more correct.

> Is there a way to
> change 2.6.x behavior to go back to the 2.4.x ? When was this change
> introduce ?

Just keep the port open when you are using it. Even in 2.4 the driver
could have been unloaded on some setups if you didn't have a port open.

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/