summaryrefslogtreecommitdiffstats
path: root/sys/geom/geom_fox.c
Commit message (Collapse)AuthorAgeFilesLines
* Don't pass error value pointer to g_read_data(9) at all if we don'tsobomax2005-11-301-1/+1
| | | | | | have any use of it. Suggested by: pjd
* Check for g_read_data(9) errors properly:sobomax2005-11-301-1/+1
| | | | | | | | | | o The only indication of error condition is NULL value returned by the function; o value pointed to by error argument is undefined in the case when operation completes successfully. Discussed with: phk
* /* -> /*- for copyright notices, minor format tweaks as necessaryimp2005-01-061-2/+3
|
* Tag all geom classes in the tree with a version number.phk2004-08-081-0/+1
|
* Use default method initialization on geoms.phk2004-08-081-4/+4
|
* Do not check error code from closing ->access() calls, we know they succeed.phk2004-02-141-4/+7
|
* Remove the absolute count g_access_abs() function since experience hasphk2004-02-121-11/+11
| | | | | | | | | | | | shown that it is not useful. Rename the relative count g_access_rel() function to g_access(), only the name has changed. Change all g_access_rel() calls in our CVS tree to call g_access() instead. Add an #ifndef BURN_BRIDGES #define of g_access_rel() for source code compatibility.
* Fix memory leak.le2004-02-061-1/+1
| | | | | | PR: kern/58634 Submitted by: le Approved by: phk
* Fix two old/new consumer confusions.phk2003-10-241-2/+2
| | | | Submitted by: Pawel Jakub Dawidek <nick@garage.freebsd.pl>
* Fix a braino memory leak.phk2003-10-221-1/+1
| | | | Found by: Pawel Jakub Dawidek <nick@garage.freebsd.pl>
* Add "GEOM_FOX", a class which detects and selects between multiplephk2003-06-181-0/+468
redundant paths to the same device. This class reacts to a label in the first sector of the device, which is created the following way: # "0123456789abcdef012345..." # "<----magic-----><-id-...> echo "GEOM::FOX someid" | dd of=/dev/da0 conv=sync NB: Since the fact that multiple disk devices are in fact the same device is not known to GEOM, the geom taste/spoil process cannot fully catch all corner cases and this module can therefore be confused if you do the right wrong things. NB: The disk level drivers need to do the right thing for this to be useful, and that is not by definition currently the case.
OpenPOWER on IntegriCloud