From owner-freebsd-current@FreeBSD.ORG  Mon Jul  4 12:37:58 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 2227D16A41F
	for <freebsd-current@freebsd.org>; Mon,  4 Jul 2005 12:37:58 +0000 (GMT)
	(envelope-from phk@phk.freebsd.dk)
Received: from haven.freebsd.dk (haven.freebsd.dk [130.225.244.222])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C2A3143D46
	for <freebsd-current@freebsd.org>; Mon,  4 Jul 2005 12:37:57 +0000 (GMT)
	(envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (unknown [192.168.48.2])
	by haven.freebsd.dk (Postfix) with ESMTP id 2CBDEBC51;
	Mon,  4 Jul 2005 12:37:55 +0000 (UTC)
To: Roman Kurakin <rik@cronyx.ru>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Mon, 04 Jul 2005 16:03:49 +0400."
	<42C925A5.8060901@cronyx.ru> 
Date: Mon, 04 Jul 2005 14:37:52 +0200
Message-ID: <29842.1120480672@phk.freebsd.dk>
Sender: phk@phk.freebsd.dk
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2005 12:37:58 -0000

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.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.