Date: Wed, 25 Feb 1998 16:17:08 -0800 (PST) From: lucasm@trilenium.com To: freebsd-gnats-submit@FreeBSD.ORG Subject: misc/5852: Page fault or error caused by writing to misconfigured /dev/sequencer Message-ID: <199802260017.QAA06078@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 5852 >Category: misc >Synopsis: Page fault or error caused by writing to misconfigured /dev/sequencer >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 25 16:20:07 PST 1998 >Last-Modified: >Originator: Lucas Madar >Organization: Trilenium Corporation >Release: FreeBsd 2.2.5-RELEASE >Environment: FreeBSD joe.trilenium.com 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE #0: Tue Feb 24 19:01:30 EST 1998 root@joe.trilenium.com:/usr/src/sys/compile/JOE i386 >Description: If /dev/sequencer exists and is not configured or not configured correctly, sending input to it causes random errors. stdout: device not configured was returned once, and the terminal died and had to be killed by a root login. The cat process used to send the output is unkillable and remains swapped out until a reboot. After a reboot, when this was tried again, sending a file to /dev/sequencer caused a page fault and a kernel panic, and the machine rebooted. >How-To-Repeat: cat (anyfile) > /dev/sequencer Problem is most severe if /dev/sequencer is world writable (anyone can do it). >Fix: Remove /dev/sequencer if you do not have it configured correctly, or make it non-world writable so only root can cause trouble :) >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802260017.QAA06078>