linux-kernel - Re: Strange problem with tty layer

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] [day] [month] [year] [list]

Message-ID: <20070217160919.GT7584@csclub.uwaterloo.ca>
Date:	Sat, 17 Feb 2007 11:09:19 -0500
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Paul Fulghum <paulkf@...rogate.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Strange problem with tty layer

On Mon, Jan 29, 2007 at 02:27:07PM -0500, Lennart Sorensen wrote:
> I have run some tests with 8 patches from Linus's 2.6 tree on top of the
> 2.6.16.25 along with a bit of debug code in the n_tty.c, which ran
> perfectly for 3 days.  I now removed the debug code to see if it will
> still run perfectly with those 8 patches.  The patches I applied in
> order are:
> 
> commit 70522e121a521aa09bd0f4e62e1aa68708b798e1
> commit 41c28ff1635e71af072c4711ff5fadd5855d48e7
> commit 1aef821a6b3aeca8c19d06aee012ed9db617d1e3
> commit ee37df7877eeaa16d7761cce64854110a7c17ad9
> commit e1a2509023785bd3199ac068ab80155aeba01265
> commit 817d6d3bceaf34c99f5343820f9b9e6021f0655c
> commit 2c3bb20f46709a0adfa7ea408013edbcab945d5a
> commit 33b37a33c242542fac2980b8ccd90977388b7a8d
> 
> Hopefully it will stay working, and actually be a solution to my tty
> problem in 2.6.16.25.
> 
> 2.6.18.2 (Debian 2.6.18-4) on the other hand was still broken, but I am
> not sure which if any of the above commits are not in that version (the
> date ranges made me think they all should be, but maybe I got the date
> of 2.6.18 wrong, or not all commits in the linux-2.6 tree are actually
> part of a given release.  I am still figuring out git).

2.6.18 does work, it failed in different ways (overruns on the fifo)
which I dealt with by ensuring disk io was synced before testing the
serial port.

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