Date: Sat, 19 Jan 2008 00:34:37 +0100 From: "Jesper Louis Andersen" <jesper.louis.andersen@gmail.com> To: "Kostik Belousov" <kostikbel@gmail.com> Cc: current@freebsd.org Subject: Re: Strange /dev/tty behaviour on 7.0-PRELEASE Message-ID: <56a0a2840801181534t57d24177o7528093c6daa995@mail.gmail.com> In-Reply-To: <20080118120816.GH57756@deviant.kiev.zoral.com.ua> References: <56a0a2840801171617r6ca60b30x9f6cebb12b523c7f@mail.gmail.com> <20080118120816.GH57756@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 18, 2008 1:08 PM, Kostik Belousov <kostikbel@gmail.com> wrote: > After your post, I could imagine the almost plausible scenario how to > get more then one /dev/tty in the listing, but the other behaviour that > looks like deadlock, isn't. > Well, your commit here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/tty_pty.c.diff?r1=1.155;r2=1.156 gratiously provided to me by Peter Wemm solved the problem I had. I think we are "talking past each other" with the lockup due to my bad choice of words: The kernel did not deadlock, but a process executed after having multiple tty's made that process hang with the ktrace I posted. The kernel itself were still running fine though anything in need of /dev/tty would hang. I hope this clears up the misconceptions. The patch fixes my problem completely. Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56a0a2840801181534t57d24177o7528093c6daa995>