Date: Sun, 18 Feb 1996 00:57:37 GMT From: dwmalone@maths.tcd.ie To: FreeBSD-gnats-submit@freebsd.org Cc: nops@maths.tcd.ie Subject: kern/1031: mount can panic system. Message-ID: <199602180057.AAA13877@synge.maths.tcd.ie> Resent-Message-ID: <199602180100.RAA08549@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 1031 >Category: kern >Synopsis: mount can panic system. >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Feb 17 17:00:01 PST 1996 >Last-Modified: >Originator: David Malone >Organization: School of Mathematics, Trinity College, Dublin, Ireland. >Release: FreeBSD 2.1-STABLE i386 >Environment: FreeBSD 2.1, I've tried the stale version and an earlier snapshot. >Description: Bad command line arguments to mount will either cause processes to hang in the kernel or panic the machine. This seems to happen whenever the device and the directory for the mount point are the same. The panic says: ufs_lock: recursive lock not eexpected, pid: whatever >How-To-Repeat: This panics our 2.1.0-RELEASE and 2.1.0-951020-SNAP system: mount /etc /etc As a normal user you can try : mkdir /tmp/x mount -t msdos /tmp/x /tmp/x This paniced my 2.1.0-951020-SNAP. >Fix: Be more carefull with what arguements you give mount ? >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602180057.AAA13877>