linux-kernel - Re: ttyACM0: 2.6.30-rc7 dies on device disconnect, strange echo (regressions)

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:	Mon, 1 Jun 2009 13:31:51 +0200
From:	Pavel Machek <pavel@....cz>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	kernel list <linux-kernel@...r.kernel.org>,
	Greg KH <greg@...ah.com>, "Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: ttyACM0: 2.6.30-rc7 dies on device disconnect, strange echo
	(regressions)

Hi!

First, thanks for quick reply.

> > > I believe this worked before; on 2.6.30-rc7, when ttyACM0 dies
> > > (openmoko in bootloader powers off) the notebook I'm running minicom
> > > on dies, too :-(. For the first time, I did not catch any messages,
> > > I'll retry the test on console.
> >
> > Nothing useful on the console...
> >
> > And it gets worse: with 2.6.30-rc7, I only get echo on character N
> > when I type character N=1. Which is extremely confusing and basically
> > makes it unusable for interactive work. This definitely worked
> > before... but it was quite long ago.

> Do you have any reason to assume these bugs are related? If not,
> please keep them separate.

Well, ok, they are probably two different bugs...

> Can you please be more specific what exactly fails?

...but it is quite easy to test for both of them and they seem to be
introduced in similar timeframe.

Steps to reproduce:

minicom /dev/ttyACM0

Bug #2: try to interactivelly communicate with the other
device. Notice that characters are echoed one character too late. You
type "hello", but only "hell" appears. You press "!", "o" appears. 

Bug #1: while minicom is still connected, pull the USB cable. Machine
locks hard.

Now, both bugs are present in 2.6.28, and 2.6.24-rc8 does not have
either problem.

It would be nice if someone could verify if it also happens with
regular USB modem -- I'm using openmoko to reproduce it.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/