From owner-freebsd-bugs@FreeBSD.ORG  Sun May  2 15:27:17 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id D689B16A4ED; Sun,  2 May 2004 15:27:17 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id AF8DE43D49; Sun,  2 May 2004 15:27:17 -0700 (PDT)
	(envelope-from rwatson@FreeBSD.org)
Received: from freefall.freebsd.org (rwatson@localhost [127.0.0.1])
	i42MRHLw008084;	Sun, 2 May 2004 15:27:17 -0700 (PDT)
	(envelope-from rwatson@freefall.freebsd.org)
Received: (from rwatson@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i42MRHEY008080;
	Sun, 2 May 2004 15:27:17 -0700 (PDT)
	(envelope-from rwatson)
Date: Sun, 2 May 2004 15:27:17 -0700 (PDT)
From: Robert Watson <rwatson@FreeBSD.org>
Message-Id: <200405022227.i42MRHEY008080@freefall.freebsd.org>
To: cherbst@hotpop.com, rwatson@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: misc/36110: dmesg output corrupt if /dev/console is busy
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 02 May 2004 22:27:18 -0000

Synopsis: dmesg output corrupt if /dev/console is busy

State-Changed-From-To: open->analyzed
State-Changed-By: rwatson
State-Changed-When: Sun May 2 15:25:33 PDT 2004
State-Changed-Why: 

This occurs because we use a single combined buffer for both kernel
messages (normally captured in the kernel's msgbuf) and logged
console output (/dev/console).  This results in a variety of problems,
and would probably be best corrected by breaking out msgbuf into two
separate buffers since their contents have different properties.

An important security issue relating to this bug/feature can be found
in bin/25337.


http://www.freebsd.org/cgi/query-pr.cgi?pr=36110