summaryrefslogtreecommitdiffstats
path: root/sys/geom/bde
Commit message (Collapse)AuthorAgeFilesLines
* Kill leading whilespace.sobomax2005-11-301-1/+1
|
* Normalize a significant number of kernel malloc type names:rwatson2005-10-311-1/+1
| | | | | | | | | | | | | | | | | | | - Prefer '_' to ' ', as it results in more easily parsed results in memory monitoring tools such as vmstat. - Remove punctuation that is incompatible with using memory type names as file names, such as '/' characters. - Disambiguate some collisions by adding subsystem prefixes to some memory types. - Generally prefer lower case to upper case. - If the same type is defined in multiple architecture directories, attempt to use the same name in additional cases. Not all instances were caught in this change, so more work is required to finish this conversion. Similar changes are required for UMA zone names.
* Comment typophk2005-07-201-1/+1
|
* stop including rijndael-api-fst.h from rijndael.h.ume2005-03-114-4/+4
| | | | this is required to integrate opencrypto into crypto.
* /* -> /*- for copyright notices, minor format tweaks as necessaryimp2005-01-063-5/+6
|
* Fix typo in a comment.brueffer2004-12-151-1/+1
| | | | MFC after: 3 days
* Fix a problem that shows up if less than the full complement ofphk2004-09-111-1/+1
| | | | | lock sectors are defined ("number_of_keys" argument to gbde init being less than 4 in the default compile).
* Respect that G_BDE_MAXKEYS is a compile time variable.phk2004-09-111-4/+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
|
* kthread_exit() no longer requires Giant, so don't force callers to acquirejhb2004-03-051-1/+0
| | | | | | Giant just to call kthread_exit(). Requested by: many
* Do not check error code from closing ->access() calls, we know they succeed.phk2004-02-141-3/+1
|
* Remove the absolute count g_access_abs() function since experience hasphk2004-02-121-4/+4
| | | | | | | | | | | | 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.
* Polish the work/state engine in preparation for HW-crypto support.phk2004-02-081-64/+65
|
* Add a missing error case return.phk2004-02-081-0/+1
| | | | Problem reported by: Flemming Jacobsen <fj@batmule.dk>
* We don't need to hold Giant to create the worker kthread.phk2004-02-071-2/+0
|
* Remove the MD5_KEY debugging toolphk2004-01-231-33/+0
|
* Interior decoration changes.phk2003-10-072-42/+39
|
* Correct bzero length so we clear the entire key structure.phk2003-09-081-1/+1
|
* Bzero the right number of bytes.phk2003-09-061-1/+1
| | | | Found by: Juergen Buchmueller <pullmoll@stop1984.com>
* Simplify the GEOM OAM api: Drop the request type, and let everythingphk2003-06-011-28/+30
| | | | | | | | hinge on the "verb" parameter which the class gets to interpret as it sees fit. Move the entire request into the kernel and move changed parameters back when done.
* Remove unused variable.phk2003-05-311-6/+0
| | | | Found by: FlexeLint
* Don't use & in front of arrays.phk2003-05-311-2/+2
| | | | Found by: FlexeLint
* Remove unused variable.phk2003-05-311-2/+0
| | | | Found by: FlexeLint
* Remove the G_CLASS_INITIALIZER, we do not need it anymore.phk2003-05-311-1/+0
|
* Re-order the the initialization slightly to improve structure.phk2003-05-051-22/+22
|
* Use a dedicated malloc(9) bucket for sector storage.phk2003-05-051-7/+9
|
* Considering that I did cast the arguments to (intmax_t) I must havephk2003-05-021-4/+4
| | | | been sleepy since I used %qd instead of %jd.
* Fix an obscure fencepost error in GBDE's sector mapping code:phk2003-04-291-0/+26
| | | | | | | | | | | | | | | For certain combinations of sectorsize, mediasize and random numbers (used to define the mapping), a multisector read or write would ignore some subset of the sectors past the first sector in the request because those sectors would be mapped past the end of the parent device, and normal "end of media" truncation would zap that part of the request. Rev 1.19+1.20 of g_bde_work.c added the check which should have alerted me to this happening. This commit maps the request correctly and adds KASSERTS to make sure things stay inside the parent device. This does not change the on-disk layout of GBDE, there is no need to backup/restore.
* Typo in last commit: Do not press xZZ to leave vi(1).phk2003-04-291-1/+1
|
* When a bio comes back from below with a zero error code, check thatphk2003-04-291-0/+4
| | | | | | | it wrote the full length. The only case where this should be able to happen is if we try to read/write past the end and the request is truncated. We obviously should never try to do that, so this code should never activate.
* I accidentally leaked this debugging tool in with my last commit.phk2003-04-281-2/+4
| | | | Disable it with a direct warning.
* Rename g_bde_get_sector() to g_bde_get_keysector() and pick up thephk2003-04-282-5/+42
| | | | offset from the work packet.
* Only attempt total cache-purge once in case of failure.phk2003-04-281-4/+3
|
* Better criteria for skipping disk reading BIO_READ work packets.phk2003-04-281-1/+2
|
* Explicitly set the sector state to JUNK if we encounter a read-error.phk2003-04-281-1/+4
|
* Bail as soon as the first write request has failed, there is no pointphk2003-04-261-2/+11
| | | | in trying the second write if the first one went nowhere.
* Appearantly UFS no longer issues BIO_DELETE requests correctly, andphk2003-04-261-0/+7
| | | | consequently trashes data. Disable BIO_DELETE handling in gbde for now.
* Do an explicit retry after we have dumped the cache, rather than aphk2003-04-251-4/+3
| | | | (potential) tail recursion.
* If on a BIO_READ request, we failed to allocate the bio for readingphk2003-04-251-6/+13
| | | | | | | | our key-sector, we would end up returning the read without an error, despite the fact that the data was not correctly decrypted. This would result in data corruption on read, but intact data still on the media.
* Fix a problem and slightly improve the ENOMEM handling:phk2003-04-251-11/+12
| | | | | | | | | | | | | Give up the entire bio as soon as we detect a problem. When we detect a problem, give up the bio by contributing the remainder with ENOMEM, rather than kicking the bio back right away. If we failed on a non-first iteration we previously could end up modifying fields in the bio after we delivered it. This could account for memory corruption (none directly reported) on machines with GBDE.
* Don't count a sector in the cache unless we manage to create it.phk2003-04-251-2/+2
|
* Rename g_bde_release_sector() to g_bde_release_keysector() and pick upphk2003-04-251-7/+9
| | | | the sector from the work item.
* Rename g_bde_read_sector() to g_bde_read_keysector() pick up the offsetphk2003-04-251-5/+5
| | | | in the work structure.
* Remove all references to BIO_SETATTR. We will not be using it.phk2003-04-031-1/+0
|
* Use sys/endian.h instead of geom_enc.c for endian-agnostfication.phk2003-04-032-17/+19
|
* Remove the old config interface now that the new OAM is functional.phk2003-04-011-153/+0
|
* Add create_geom and destroy_geom methods.phk2003-03-291-0/+159
|
* Forward compatibility: NULL check the passed in meta argument.phk2003-03-251-1/+1
|
* Premptively change initializations of struct g_class to use C99phk2003-03-241-3/+2
| | | | | sparse struct initializations before we extend the struct with new OAM related member functions.
OpenPOWER on IntegriCloud