From owner-freebsd-bugs@FreeBSD.ORG Tue May 17 14:10:06 2005 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3853D16A4D0 for ; Tue, 17 May 2005 14:10:06 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B605443DC9 for ; Tue, 17 May 2005 14:10:05 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j4HEA2XB095349 for ; Tue, 17 May 2005 14:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j4HEA2BV095346; Tue, 17 May 2005 14:10:02 GMT (envelope-from gnats) Resent-Date: Tue, 17 May 2005 14:10:02 GMT Resent-Message-Id: <200505171410.j4HEA2BV095346@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Ronny lam Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C952F16A4CE for ; Tue, 17 May 2005 14:04:54 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id A323343D8A for ; Tue, 17 May 2005 14:04:54 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j4HE4rQL023309 for ; Tue, 17 May 2005 14:04:53 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j4HE4rBJ023308; Tue, 17 May 2005 14:04:53 GMT (envelope-from nobody) Message-Id: <200505171404.j4HE4rBJ023308@www.freebsd.org> Date: Tue, 17 May 2005 14:04:53 GMT From: Ronny lam To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: kern/81161: Images mounted through mdconfig on a read-only fs can be modified X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2005 14:10:06 -0000 >Number: 81161 >Category: kern >Synopsis: Images mounted through mdconfig on a read-only fs can be modified >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: Tue May 17 14:10:02 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Ronny lam >Release: 5.4 >Organization: Snow B.V. >Environment: FreeBSD helix.kateri.demon.nl 5.4-RELEASE-p1 FreeBSD 5.4-RELEASE-p1 #2: Tue May 17 14:26:04 CEST 2005 root@helix.kateri.demon.nl:/usr/local/obj/usr/local/src/sys/HELIX i386 >Description: When mounting an image through mdconfig which resides on a read-only filesystem, it is possible to changes the md-filesystem and thus change the read-only underlying filesystem. This could be by design but looks like a problem to me. >How-To-Repeat: boot single-user, the root filesystem is readonly mdconfig -a -t vnode -f boot.flp mount /dev/md0 /mnt touch /mnt/hello ls /mnt mount, root filesystem is still read-only, /mnt is read-write umount /mnt mdconfig -d -u 0 mdconfig -a -t vnode -f boot.flp mount /dev/md0 /mnt ls /mnt >Fix: >Release-Note: >Audit-Trail: >Unformatted: