Date: Thu, 23 Apr 1998 16:06:11 -0700 (PDT) From: jcwells@u.washington.edu To: freebsd-gnats-submit@FreeBSD.ORG Subject: bin/6401: user error while mounting causes panic Message-ID: <199804232306.QAA15002@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 6401 >Category: bin >Synopsis: user error while mounting causes panic >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 23 16:10:01 PDT 1998 >Last-Modified: >Originator: Jason Wells >Organization: na >Release: 2.2.2-RELEASE >Environment: FreeBSD s8-37-26.student.washington.edu 2.2.2-RELEASE FreeBSD 2.2.2-RELEASE #0: Wed Apr 22 15:23:34 PDT 1998 root@s8-37-26.student.washington.edu:/usr/src/sys/compile/BRONCO i386 >Description: I did this typo. # mount_cd9660 /dev/wcd0c /dev I got, "panic ufs_lock resursive lock not expected pid 158" >How-To-Repeat: Keep trying the above command. >Fix: Don't commit the error on the command line. -OR- Perhaps mount might check for a recursive lock prior to allowing the user to cause a panic. (???) I concede that this is user error. But... a repeatable panic is problematic. I asked -questions if this deserved a send-pr. Some said "pilot error" did not deserve send-pr. Some said a user error causing panic was "against the unix philosophy." I leave it to you to decide if this problem has any merit. I apologize in advance if this pr is dubious. >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?199804232306.QAA15002>