From owner-freebsd-hackers@FreeBSD.ORG  Tue Mar 23 21:27:58 2010
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A526C1065672
	for <freebsd-hackers@freebsd.org>; Tue, 23 Mar 2010 21:27:58 +0000 (UTC)
	(envelope-from jhb@freebsd.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 759308FC0A
	for <freebsd-hackers@freebsd.org>; Tue, 23 Mar 2010 21:27:58 +0000 (UTC)
Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net
	[66.111.2.69])
	by cyrus.watson.org (Postfix) with ESMTPSA id 2912A46B1A;
	Tue, 23 Mar 2010 17:27:58 -0400 (EDT)
Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9])
	by bigwig.baldwin.cx (Postfix) with ESMTPA id 77D418A021;
	Tue, 23 Mar 2010 17:27:57 -0400 (EDT)
From: John Baldwin <jhb@freebsd.org>
To: "Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?=" <des@des.no>
Date: Tue, 23 Mar 2010 17:27:45 -0400
User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; )
References: <da48cf211003230218n56794f0bs27eef860efc0da3e@mail.gmail.com>
	<201003231000.58961.jhb@freebsd.org> <86zl1y4uiu.fsf@ds4.des.no>
In-Reply-To: <86zl1y4uiu.fsf@ds4.des.no>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201003231727.45357.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1
	(bigwig.baldwin.cx); Tue, 23 Mar 2010 17:27:57 -0400 (EDT)
X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-1.7 required=4.2 tests=AWL,BAYES_00 autolearn=ham
	version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx
Cc: freebsd-hackers@freebsd.org, Dmitry Krivenok <krivenok.dmitry@gmail.com>
Subject: Re: Strange behavior of kernel module (output terminated)
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 21:27:58 -0000

On Tuesday 23 March 2010 5:07:05 pm Dag-Erling Sm=C3=B8rgrav wrote:
> John Baldwin <jhb@freebsd.org> writes:
> > Dag-Erling Sm=C3=B8rgrav <des@des.no> writes:
> > > I'm not sure it's such a good idea to use uprintf() here.  The event
> > > handler can be called in non-process context.
> > If you are doing a kldload post-boot it is actually done from some sort=
 of=20
> > process context.  We run module handlers synchronously from the kldload=
(2)=20
> > syscall.
>=20
> Sure, but not when the module is loaded by the boot loader (note "can",
> not "will")

=46or the purposes of writing a dummy test kld that you know you will load =
via
kldload it is ok though. :)

=2D-=20
John Baldwin