summaryrefslogtreecommitdiffstats
path: root/sys/geom/bde
Commit message (Collapse)AuthorAgeFilesLines
* MFC r306279: Use g_wither_provider() where applicable.mav2016-10-061-1/+1
| | | | | It is just a helper function combining G_PF_WITHER setting with g_orphan_provider().
* sys/geom: spelling fixes in comments.pfg2016-04-291-1/+1
| | | | No functional change.
* sys: use our roundup2/rounddown2() macros when param.h is available.pfg2016-04-211-1/+1
| | | | | | | | | | rounddown2 tends to produce longer lines than the original code and when the code has a high indentation level it was not really advantageous to do the replacement. This tries to strike a balance between readability using the macros and flexibility of having the expressions, so not everything is converted.
* Replace sys/crypto/sha2/sha2.c with lib/libmd/sha512c.callanjude2015-12-274-4/+4
| | | | | | | | | | | | | | | | | | cperciva's libmd implementation is 5-30% faster The same was done for SHA256 previously in r263218 cperciva's implementation was lacking SHA-384 which I implemented, validated against OpenSSL and the NIST documentation Extend sbin/md5 to create sha384(1) Chase dependancies on sys/crypto/sha2/sha2.{c,h} and replace them with sha512{c.c,.h} Reviewed by: cperciva, des, delphij Approved by: secteam, bapt (mentor) MFC after: 2 weeks Sponsored by: ScaleEngine Inc. Differential Revision: https://reviews.freebsd.org/D3929
* Constify the AES code and propagate to consumers. This allows us todes2014-11-101-3/+3
| | | | | | update the Fortuna code to use SHAd-256 as defined in FS&K. Approved by: so (self)
* Translate the errno to gctl_error() texts.phk2014-11-091-0/+17
| | | | Spotted by: mwlucas
* - Don't pass geom and provider names as format strings.jh2012-11-201-1/+1
| | | | | | | - Add __printflike() attributes. - Remove an extra argument for the g_new_geomf() call in swapongeom_ev(). Reviewed by: pjd
* Remove unneeded G_PF_CANDELETE flag.ed2012-08-281-8/+0
| | | | | This flag is only used by GEOM so it can be propagated to the character device's SI_CANDELETE. Unfortunately, SI_CANDELETE seems to do nothing.
* Fix orphan() methods of several GEOM classes to not assume that theretrasz2012-07-071-5/+1
| | | | | | | | | is an error set on the provider. With GEOM resizing, class can become orphaned when it doesn't implement resize() method and the provider size decreases. Reviewed by: mav Sponsored by: FreeBSD Foundation
* Add some FEATURE macros for various GEOM classes.netchild2011-02-251-0/+3
| | | | | | | | | | | No FreeBSD version bump, the userland application to query the features will be committed last and can serve as an indication of the availablility if needed. Sponsored by: Google Summer of Code 2010 Submitted by: kibab Reviewed by: silence on geom@ during 2 weeks X-MFC after: to be determined in last commit with code from this project
* Rename the kthread_xxx (e.g. kthread_create()) callsjulian2007-10-202-2/+2
| | | | | | | | | | | to kproc_xxx as they actually make whole processes. Thos makes way for us to add REAL kthread_create() and friends that actually make theads. it turns out that most of these calls actually end up being moved back to the thread version when it's added. but we need to make this cosmetic change first. I'd LOVE to do this rename in 7.0 so that we can eventually MFC the new kthread_xxx() calls.
* Commit the results of the typo hunt by Darren Pilgrim.yar2006-08-041-1/+1
| | | | | | | | | | This change affects documentation and comments only, no real code involved. PR: misc/101245 Submitted by: Darren Pilgrim <darren pilgrim bitfreak org> Tested by: md5(1) MFC after: 1 week
* 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.
OpenPOWER on IntegriCloud