From owner-freebsd-commit  Sat Mar  9 16:20:47 1996
Return-Path: owner-commit
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA07891
          for freebsd-commit-outgoing; Sat, 9 Mar 1996 16:20:47 -0800 (PST)
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA07854
          for cvs-all-outgoing; Sat, 9 Mar 1996 16:20:40 -0800 (PST)
Received: (from mpp@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA07805
          Sat, 9 Mar 1996 16:20:30 -0800 (PST)
Date: Sat, 9 Mar 1996 16:20:30 -0800 (PST)
From: Mike Pritchard <mpp>
Message-Id: <199603100020.QAA07805@freefall.freebsd.org>
To: CVS-committers, cvs-all, cvs-sbin
Subject: cvs commit:  src/sbin/mount mount.c
X-Loop: owner-cvs-all@FreeBSD.ORG
Sender: owner-commit@FreeBSD.ORG
X-Loop: owner-commit@FreeBSD.ORG
Precedence: bulk

mpp         96/03/09 16:20:29

  Modified:    sbin/mount  mount.c
  Log:
  Do not allow the caller to specify the same path for the special
  device file and the mount point.  This prevents the "unexpected recursive
  lock" panic from happening.
  
  This is a temporary fix.  A kernel fix would be much much more ugly than
  this, and still wouldn't be the "right" way to fix it.  After some
  of Terry's file system rework is installed, it will be possible to
  properly fix this problem in a clean manner.  Until then,
  this change should prevent use from getting a problem report
  on this every month or so (and I just noticed that someone in
  one of the freebsd news groups was complaining about this problem, too).
  
  Revision  Changes    Path
  1.10      +19 -0     src/sbin/mount/mount.c