From owner-freebsd-current Tue Jul 13 5:40:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id F1F8814FD6 for ; Tue, 13 Jul 1999 05:40:39 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id OAA08327 for ; Tue, 13 Jul 1999 14:40:35 +0200 (MET DST) Date: Tue, 13 Jul 1999 14:40:32 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD current mailing list Subject: PR with patch, any takers? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [PATCH] mountd(8) can apply flags to wrong filesystem [Includes a patch, patch looks like it applies to mountd.c from current] Description When mountd(8) receives a HUP signal, it stops all NFS exporting of filesystems, and then passes the export rules from /etc/exports via a number of mount(2) invocations. In order to handle cases where the path listed in /etc/exports is not the real mount point, mountd repeatedly removes the last path component until the mount call succeeds. Due to insuffient error checking, mountd can miss the real mount point, and apply the flags from a mounted filesystem to the underlying one. In the case we have seen, a forgotten entry in /etc/exports resulted in mountd setting the nodev flag on / every time mountd was sent a HUP signal. Any takers for it? http://www.freebsd.org/cgi/query-pr.cgi?pr=7872 Cheers, Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message