linux-kernel - Re: 2.6.25.3: serial problem (minicom)

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: <alpine.LNX.1.00.0806150032050.1283@hani.compact.internal>
Date:	Sun, 15 Jun 2008 02:04:42 -0500 (CDT)
From:	"R.L. Horn" <lists@...tcheap.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.25.3: serial problem (minicom)

On Sat, 14 Jun 2008, Alan Cox wrote:

> What happens after you go from B0->Banythingelse should depend on the
> termios settings at that point. This sounds like a bug therefore.
>
> If you want that behaviour intentionally set B0, after this termios
> call then set CLOCAL before changing the baud back.

I'm not seeing any change in behavior with different combinations of 
CLOCAL.  As it happens, minicom sets CLOCAL first thing so as to keep 
SIGHUP signals from being generated.

But, then, what is the relationship between CLOCAL and DTR/RTS supposed to 
be?  Presumably, it should prevent a SIGHUP from being raised when DSR 
goes low, but beyond that, it all seems rather ill-defined.  Throw in B0, 
which the SUS strongly implies should unconditionally lower DTR and RTS, 
and the CRTSCTS flag, and the waters really get murky.  It looks to me 
like the only thing you can say for certain is that CLOCAL will cause DSR 
to be ignored...and for anything else you're on your own.

Mind you, all this just suggests that POSIX kinda sucks, which is hardly 
an earth-shattering revelation.

> I'll take a look at this next week.

It would be much appreciated.  Thanks.
--
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/