From owner-freebsd-current Fri Oct 12 7:29:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id F316D37B407 for ; Fri, 12 Oct 2001 07:29:15 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id AAA18981; Sat, 13 Oct 2001 00:28:44 +1000 Date: Sat, 13 Oct 2001 00:27:58 +1000 (EST) From: Bruce Evans X-X-Sender: To: Dag-Erling Smorgrav Cc: Doug Barton , Subject: Re: Strike three, you're out In-Reply-To: Message-ID: <20011013001912.J49532-100000@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 12 Oct 2001, Dag-Erling Smorgrav wrote: > Doug Barton writes: > > Reported on 9/30: > > panic: blockable sleep lock (sx) allproc @ > > /usr/local/src/sys/kern/kern_proc.c:212 > > > > According to BDE, "This is a well-know bug in printf(9). The TIOCCONS > > ioctl always gave non-deterministic crashes. Now it gives determinstic > > panics when > > pintf() is called while sched_lock is held." That's the only discussion > > about it, no fixes, no suggestions. > > Remove UCONSOLE from kernel config. This has been discussed to death > several times on the lists. That only prevents non-root from triggering the bug. What an evil option. It has always been enabled in GENERIC although it has always implemented panics and security holes. It has always been enabled in LINT/NOTES although it is a negative option. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message