NetBSD Problem Report #11515

Received: (qmail 5460 invoked from network); 18 Nov 2000 15:30:09 -0000
Message-Id: <200011181530.eAIFU7M09127@brandenburg.cs.mu.OZ.AU>
Date: Sat, 18 Nov 2000 22:30:07 +0700 (ICT)
From: kre@munnari.OZ.AU
To: gnats-bugs@gnats.netbsd.org
Subject: vnconfig requires read/write access to the underlying file
X-Send-Pr-Version: 3.95

>Number:         11515
>Category:       kern
>Synopsis:       vnconfig requires reqd/write access to the file
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    nat
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Nov 18 15:31:01 +0000 2000
>Closed-Date:    Tue Jun 27 00:08:25 +0000 2017
>Last-Modified:  Tue Jun 27 00:08:25 +0000 2017
>Originator:     Robert Elz
>Release:        1.5_BETA
>Organization:
	University of Melbourne
>Environment:

System: NetBSD brandenburg.cs.mu.OZ.AU 1.5_BETA NetBSD 1.5_BETA (GATEWAY) #2: Thu Oct 26 05:55:17 EST 2000 root@:/usr/src/sys/arch/i386/compile/GATEWAY i386


>Description:
	vnconfig (the vnd pseudo-device) requires read-write
	access to the underlying file.   It shouldn't.

>How-To-Repeat:

	Accidentally write an iso inage as a file into a CD, instead
	of using the image file as the CD (ie: the CD ends up containing
	a single file, file.iso) - attempt to use vnd0 to access the
	contents of the file (before writing to the CD the file could
	be accessed that way).

	Observe...

	mount -r -t cd9660 /dev/cd0a /cdrom
	cd /cdrom
	vnconfig -c vnd0 file.iso
	vnconfig: /dev/rvnd0d: VNDIOCSET: Read-only file system

	If the underlying file is read-only (or on a read only device)
	the vnd interface should simply make a read-only device

>Fix:
>Release-Note:
>Audit-Trail:
From: Nat Sloss <nathanialsloss@yahoo.com.au>
To: "gnats-bugs" <gnats-bugs@netbsd.org>
Cc: 
Subject: Re: kern/11515 - vnconfig requires reqd/write access to the file
Date: Wed, 15 Jan 2014 14:32:10 +1100

 Hi,

 I've tested this with a read only nfs file system on NetBSD 6.1.1 although I 
 had to specify -r to vnconfig the vnd creation succeeded.

 The -r option has existed since rev 1.26 (2003) of vnconfig.c.

 This didn't exist when the PR was submitted and I think the -r option 
 addresses this PR unless it is desirable to have vnconfig fall back to a read 
 only device creation.

 Regards,

 Nat.

From: Robert Elz <kre@munnari.OZ.AU>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/11515 - vnconfig requires reqd/write access to the file
Date: Wed, 15 Jan 2014 12:19:53 +0700

 I haven't tried vnconfig on a read only file fora very long time ... but
 yes, an option to vnconfig to allow it would be just fine.   Certainly there's
 little benefit in keeping ancient PRs like this one open - especially if
 they're fixed!

 kre

Responsible-Changed-From-To: kern-bug-people->nat
Responsible-Changed-By: nat@NetBSD.org
Responsible-Changed-When: Tue, 27 Jun 2017 00:08:25 +0000
Responsible-Changed-Why:
Take.


State-Changed-From-To: open->closed
State-Changed-By: nat@NetBSD.org
State-Changed-When: Tue, 27 Jun 2017 00:08:25 +0000
State-Changed-Why:
Since this PR was opened vnconfig now has the -r switch for read-only access.


>Unformatted:

Home	PR Database Search