From owner-freebsd-current@FreeBSD.ORG Mon Jul 4 13:53:23 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04ECB16A41C for ; Mon, 4 Jul 2005 13:53:23 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 724E143D45 for ; Mon, 4 Jul 2005 13:53:22 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru (8.13.0/vak/3.0) id j64DoJkK001202 for freebsd-current@freebsd.org.checked; Mon, 4 Jul 2005 17:50:19 +0400 (MSD) (envelope-from rik@cronyx.ru) Received: from [144.206.181.94] (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru (8.13.0/vak/3.0) with ESMTP id j64DnrFG001180; Mon, 4 Jul 2005 17:49:53 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <42C93E8E.4010408@cronyx.ru> Date: Mon, 04 Jul 2005 17:50:06 +0400 From: Roman Kurakin User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <29842.1120480672@phk.freebsd.dk> In-Reply-To: <29842.1120480672@phk.freebsd.dk> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: TTY code problems in current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jul 2005 13:53:23 -0000 Poul-Henning Kamp wrote: >In message <42C925A5.8060901@cronyx.ru>, Roman Kurakin writes: > > >>Hi, >> >> I observe some problems with my driver in async mode. >>One of the panics I see is in function putc() from tty_subr.c. >>It seems that this panic due to the fact that clist is not protected >>by any locks if driver works in smpsafe mode without Giant. >> >> The panic occur beacuse of pointer modification (the new value >>of the pointer eq. to NULL. >>Any comments? >> >> > >We do not support smpsafe tty drivers yet. > > Hm, I was sure we are after you patches. But I didn't really check you patches.Mostly the the API changes, not internals. Do you work on it or your work was only code cleanup? Is there any plans to make them smpsafe on RELENG_6? Thanks, rik