| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
- Add __printflike() attributes.
- Remove an extra argument for the g_new_geomf() call in swapongeom_ev().
Reviewed by: pjd
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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.
|
| |
|
|
|
|
| |
this is required to integrate opencrypto into crypto.
|
| |
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
lock sectors are defined ("number_of_keys" argument to gbde init being
less than 4 in the default compile).
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Giant just to call kthread_exit().
Requested by: many
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Problem reported by: Flemming Jacobsen <fj@batmule.dk>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Found by: Juergen Buchmueller <pullmoll@stop1984.com>
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
|
|
|
| |
Found by: FlexeLint
|
| |
|
| |
|
| |
|
|
|
|
| |
been sleepy since I used %qd instead of %jd.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Disable it with a direct warning.
|
|
|
|
| |
offset from the work packet.
|
| |
|
| |
|
| |
|
|
|
|
| |
in trying the second write if the first one went nowhere.
|
|
|
|
| |
consequently trashes data. Disable BIO_DELETE handling in gbde for now.
|
|
|
|
| |
(potential) tail recursion.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
the sector from the work item.
|
|
|
|
| |
in the work structure.
|