Date: Thu, 29 Jul 1999 15:40:05 GMT From: "Julian Stacey" <jhs@jhs.muc.de> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/12884: panic: lockmgr: locking against myself - from amd with nfs Message-ID: <199907291540.PAA03752@jhs.muc.de>
next in thread | raw e-mail | index | archive | help
>Number: 12884 >Category: kern >Synopsis: Hot to panic FreeBSD-3.2-Release >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jul 30 01:50:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Julian H. Stacey jhs@freebsd.org >Release: FreeBSD 3.2-RELEASE i386 >Organization: >Environment: 3.2-Rel, nfs & amd >Description: How to panic the kernel: >How-To-Repeat: amd -p -k i386 -l syslog -a /a /host /etc/amd.map # from rc.conf grep `hostname -s` /etc/exports # note removing hostname # does not prevent a crash ln -s .. /a/`hostname -s` wall warn all users we are about to crash echo now see panic: lockmgr: locking against myself ls /host/`hostname -s` # panic occurs OK, it's silly to do ln -s .. /a/`hostname -s` but it's unfortunate that it panics. (I did the ln on a spare box while experimenting to try to find some way to have /host/* mount the other hosts, but /host/`hostname -s` just be root (or better "..") as I use sitewide addresses like /host/some_host/usr3/..... & I want the access to be a more efficient ufs direct in the one case where the host happens to be local - I haven't found a solution to that yet BTW) >Fix: Maybe AMD should at startup do chmod a-w o-w /a ; chown 0 /a >Release-Note: >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?199907291540.PAA03752>