From nobody@FreeBSD.org  Tue May 17 14:04:54 2005
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C952F16A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; 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 <freebsd-gnats-submit@FreeBSD.org>; 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 <freebsd-gnats-submit@FreeBSD.org>; 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 <rlam@snow.nl>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Images mounted through mdconfig on a read-only fs can be modified
X-Send-Pr-Version: www-2.3

>Number:         81161
>Category:       kern
>Synopsis:       [md] Images mounted through mdconfig on a read-only fs can be modified
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    jh
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue May 17 14:10:02 GMT 2005
>Closed-Date:    Sun Feb 21 11:47:40 UTC 2010
>Last-Modified:  Sun Feb 21 11:47:40 UTC 2010
>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:
State-Changed-From-To: open->feedback 
State-Changed-By: jh 
State-Changed-When: Sun Jan 17 16:29:08 UTC 2010 
State-Changed-Why:  
I was unable to reproduce this. Do you still see the problem on recent 
FreeBSD versions? 


Responsible-Changed-From-To: freebsd-bugs->jh 
Responsible-Changed-By: jh 
Responsible-Changed-When: Sun Jan 17 16:29:08 UTC 2010 
Responsible-Changed-Why:  
Track. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=81161 
State-Changed-From-To: feedback->closed 
State-Changed-By: jh 
State-Changed-When: Sun Feb 21 11:47:38 UTC 2010 
State-Changed-Why:  
Feedback timeout. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=81161 
>Unformatted:
