summaryrefslogtreecommitdiffstats
path: root/sys/dev/vnd.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Initialize the dv_xname at attach time, so that we don't have to doderaadt2011-06-021-24/+9
| | | | | | this work later. Since the disk always has the same name (the different between svnd and vnd went away), we don't need to do this late anymore. Spotted with matthew.
* In vndclear(), clear all the flag bits. Leaving around a VNF_WLABEL bitderaadt2011-06-021-2/+2
| | | | | | is stupid (verified to be the case). Other flag bits might have lived longer than they should as well, with unknown consequences. Spotted with matthew, too.
* Initialize the dv_unit, because disk_attach will want it later. Beforederaadt2011-06-021-1/+2
| | | | | we were probably only ever reading labels off vnd0. Oops. Spotted by matthew
* Do not bzero the softc when doing VNDIOCCLR, because that trashes thederaadt2011-06-021-7/+3
| | | | | rw_lock and the device_ref Discussed with thib and matthew
* device_ref() by hand, since this is a pseudo-device and was not attachedderaadt2011-06-021-1/+2
| | | | | through config_attach() ok matthew jsing
* Change a few of the more common disk drivers (sd, cd, wd, rd, and vnd)matthew2011-05-311-2/+2
| | | | | | | | | | | | | | | | | | | to return EBUSY if the user tries to modify an open partition's offset or size. Only sadness can result if a user tries this, and rejecting it prevents a race between sdstart() and sdstrategy(). Curiously, there was already code in the kernel and in disklabel(8) to detect/handle this, but it was effectively disabled because the disk drivers always used something like "/* sc->sc_dk.dk_openmask */ 0", and this commented out code has existed since even r1.1 in NetBSD. I had no problems building a release and messing around with disklabel(8) for a bit with this diff. Canarying the more common MI disk drivers until we gain confidence that there aren't any regressions, then we can switch the remaining drivers. "I am surprised you got me convinced that this stuff is safe" deraadt@ ok krw@
* Remove vndshutdown. It is unused.oga2011-05-301-12/+1
| | | | ``sure'' deraadt@
* Remove backwards compatibility for svnd. All new operations must use thederaadt2011-04-251-6/+2
| | | | | | vnd devices nodes, which impliment svnd functionality -- that being the only thing which vnd now supports. Confused? Don't worry, it is documented. ok krw thib
* Remove now unused vndiodone(). ok deraadt@miod2011-04-231-40/+1
|
* The previous code only prevented the vnd from being opened for write injsing2011-04-231-8/+1
| | | | | both simple and non-simple mode. Restore this behaviour by removing the openmask check.
* backout the miod change since it is wrongderaadt2011-04-231-6/+4
|
* Fix regression in vndopen() behaviour introduced in previous commit.miod2011-04-221-4/+6
|
* remove the old style by-pass-the-buffer-cache vnd code.thib2011-04-181-228/+51
| | | | | | this will treat vndX the same as svndX. ok and gcc2 fixes from deraadt@
* Remove bufqs from vnds, as the disk that houses the imagethib2011-04-021-88/+45
| | | | | | | | | backing the vnd also has a bufq. So the buf is just passed between the vnd bufq and the disk bufq (almost immediately). Also see previous revision for more insight. OK deraadt@, dlg@
* A vnd buf doesn't only go through the vnd bufq but also the bufqthib2011-02-151-1/+7
| | | | | | | | | | | | | | for the device on which the vnd image resides on, this has the effect that a bufq_done call is done in the context of the underlaying bufq, setting b_bq to NULL, meaning there is never a bufq_done call done for the vnd bufq so the outstanding count never decreses. Add one in vndiodone. This fixes the suspsend issues krw@ was running into. ok tedu@, krw@ nod from miod@ on the commit.
* init and destory the bufq in the ioctl handler, asthib2011-01-061-2/+3
| | | | | | | | the softc is zero'ed when the vnd is unconfigured; otherwise we blow up when configuring a vnd the second time since the bufq structure is kaputt. found by and OK krw@
* cut vnd over to using bufq's again.thib2011-01-051-22/+15
| | | | OK dlg@, beck@, krw@.
* When configuring a vnd(4) disk, populate the disk name based on the modejsing2010-12-221-2/+14
| | | | | | | in which it was configured. If this is a "safe" vnd disk the name should be "svndX" whereas a standard vnd disk should be named "vndX". ok deraadt@ todd@ thib@
* All users of physio(9) now pass NULL as the buf pointer argument, somatthew2010-09-221-3/+3
| | | | | | | no point in keeping it around. "i like this" thib@ (a while back); ok krw@ and oga@; reminder to update the man page and tweaks jmc@
* Store a struct device pointer within struct disk and populate this whenjsing2010-09-081-2/+2
| | | | | | | disk_attach() is called by the device driver. We will be building on this shortly. ok deraadt@ krw@
* Garbage collect struct dkdriver.matthew2010-08-281-4/+1
| | | | ok miod@; "please go ahead" jsing@
* Instead of trying to biowait on a buf that has errored, do thethib2010-07-221-10/+15
| | | | | | | | | | | | right thing, throw it away by marking it as B_INVAL and setting the B_ERROR flag and b_error to the errno that was returned. B_RAW doesn't matter there. Issue report my mlarkin@, this diff tested and confirmed to fix the issue by mlarkin also, thanks! OK krw@, beck@, deraadt@
* leases have expired. (remove a comment).thib2010-07-011-2/+1
|
* for the allocated buf, set the b_bq flag to NULL so we do notthib2010-07-011-1/+2
| | | | call bufq_done in biodone.
* dont let sys/ioctl.h imply that you get the ioctls in dkio.h. thisdlg2010-05-181-1/+2
| | | | | | | | | | | gets rid of #include <sys/dkio.h> in sys/ioctl.h and adds #include <sys/dkio.h> to the places that actually want and use the disk ioctls. this became an issue when krw@'s X build failed when he was testing a change to dkio.h. tested by krw@ help from and ok miod@
* Recycle unused disklabel fields in order to create a disklabel uniquejsing2010-04-231-3/+1
| | | | | | | identifier, allowing the disk to be identified without relying on the device name. ok deraadt@ krw@ beck@ marco@ todd@
* - fix format strings for values that are daddr64_tjasper2009-08-241-4/+4
| | | | ok otto@, agreed by deraadt@
* Replace the error strings that were being passed around with much simplerderaadt2009-08-131-11/+4
| | | | | | | | | errnos. Note that the error strings are being ignored, since we long ago decided to not spam the console, and there is no other nice way to use the errors (without changing the ioctls to pass it back) The errno is now useful, since we can pass b_error from failing IO up, and the drive can decide how to use that ok miod
* Revert bufq's. this is inline with the major midlayer reverts thatthib2009-06-171-14/+14
| | | | | | have been going on. this appears to bring us back to stable state. lots of testing by oga and ariane and my self.
* Add DIOCRLDINFO to those drivers previously deprived.krw2009-06-041-1/+11
| | | | Noticed by & ok deraadt@
* add a flexible buffer queue (bufq) api, based on the never usedthib2009-06-031-14/+14
| | | | | | | | | one by tedu@. It doesn't do anything smart yet, it just uses plain old disksort. we also keep the old method of queueing bufs since some miods have crazy MD drivers that need some love. ok beck@, art@ tested by many on many archs.
* Replace -s (sector size) option with more general -t (disktype)krw2008-09-031-12/+11
| | | | | | | | | | | option which makes the vnd device emulate the geometry of the specified disktab(5) entry. No change in behaviour or geometry unless -t is used. API for vnd configuration ioctl (VNDIOCSET) changes, so mount_vnd must be in sync with kernel. Tested & ok jsing@ 'Lovely' deraadt@
* Allow the sector size to be specified by the user when configuring ajsing2008-08-141-16/+37
| | | | | | | | | | vnd(4) device, via a new -s option to vnconfig/mount_vnd. This allows us to create disklabels and file systems that are suitable for use on devices that have a non-512 byte sector size (eg. CDROMs). With help from krw@ and feedback from pedro@. ok krw@, pedro@
* Correct cases of mishandling of pending reads and writes to preventbeck2008-07-231-1/+3
| | | | | | | | | | | | | them going negative - this consists of identifying a number of cases of IO not going through the buffer cache and marking those buffers with B_RAW - as well as fixing nfs_bio to show pending writes and reads through the buffer cache via NFS still has a problem with mishandling the counters I believe in the async/sync fallback case where counters stay positive which will be addressed seperately. ok tedu@ deraadt@
* Add DIOCGPDINFO support. 'disklabel -d svnd0' now works.krw2008-07-201-1/+7
|
* Use DEV_BSIZE (defined as 512) instead of 512 when initializing thekrw2008-06-291-2/+2
| | | | | | disklabel's d_secsize. ok millert@ marco@
* Change XXgetdisklabel() to the 'normal' four parameter model tokrw2008-03-241-6/+6
| | | | | | prepare for adding missing DIOC* ioctl's. No functional change.
* more remove unneeded declarations that shadows existing vars; ok by many.fgsch2007-10-151-2/+2
|
* make safe vnds work on block devices.fkr2007-09-291-6/+53
| | | | | from Piotr Durlej, tested by henning@, krw@, thib@ and myself ok thib@, grunk@, krw@
* There is no such word as `detatch'.mk2007-09-121-2/+2
| | | | ok mglocker
* KNFgilles2007-09-111-2/+2
| | | | prompted and "much better" by marco@, ok pyr@
* more M_ZERO changesgilles2007-09-081-3/+2
| | | | ok pyr@ and krw@
* b_cylinder does not need to be set on the callpath down into drivers.deraadt2007-06-201-10/+5
| | | | cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
* all drivers should spoof version 1 labelsderaadt2007-06-081-1/+2
|
* now that all partition size/offsets are potentially 64-bit, change thederaadt2007-06-061-6/+6
| | | | | | | type of all variables to daddr64_t. this includes the APIs for XXsize() and XXdump(), all range checks inside bio drivers, internal variables for disklabel handling, and even uvm's swap offsets. re-read numerous times by otto, miod, krw, thib to look for errors
* use six new macros to access & store the 48-bit disklabel fields relatedderaadt2007-06-051-4/+4
| | | | | to size. tested on almost all machines, double checked by miod and krw next comes the type handling surrounding these values
* Don't initialize d_partitions[RAW_DISK] just before callingkrw2007-06-011-6/+1
| | | | | | readdisklabel(), since all readdisklabel()'s do that already. ok deraadt@
* Use VNDLABELDEV() and not DISKLABELDEV() in writedisklabel() sincekrw2007-05-121-2/+2
| | | | | VNDLABELDEV() is used in readdisklabel(). VNDLABELDEV() preserves the vndsimple() property encoded in the device.
* Replace expansions of DISKLABELDEV() with DISKLABELDEV(). Shorter, andkrw2007-04-291-3/+2
| | | | | | more consistant. No change to code. ok miod@
* include rwlock.h ourselves, better than depending on it getting pickedtedu2007-03-251-1/+2
| | | | up elsewhere
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.