kernel/dm: Include <sys/param.h> first.

Allow the <dev/disk/dm/dm.h> to include common headers first.

sys/dev/disk/dm: Make init/destroy handlers optional

Some targets don't need to do anything in init/destroy handler,
as there is no private data to init/cleanup, so make them optional.

table_en->ta

sys/dev/disk/dm: Make init/destroy handlers optional

Some targets don't need to do anything in init/destroy handler,
as there is no private data to init/cleanup, so make them optional.

table_en->target_config can be set to NULL regardless of destroy
handler or its result.

show more ...

sys/dev/disk/dm: Cleanup header includes

sys/dev/disk/dm: Cleanups

* Fix comments.
* Add a blank line between functions.
* Some minor fixes on dm core.

sys/dev/disk/dm: Fix/refactor alloc/free functions [6/6]

Rename dm_target_rem() to dm_target_remove() for consistency.

sys/dev/disk/dm: Fix/refactor alloc/free functions [5/6]

Add dm_target_free().

sys/dev/disk/dm: Fix/refactor alloc/free functions [4/6]

dm_target_alloc() takes char *name, but does nothing with it.
Add strlcpy and remove strlcpy from each target's init().

sys/dev/disk/dm: Check if target has registered handlers

Define which handlers are mandatory or optional.
init(), destroy(), strategy() are (or should be) mandatory.
Others aren't needed by all targ

sys/dev/disk/dm: Check if target has registered handlers

Define which handlers are mandatory or optional.
init(), destroy(), strategy() are (or should be) mandatory.
Others aren't needed by all targets hence should be optional.

Add sanity checks in dm_target_insert() to make sure targets
have implemented and registered mandatory handlers.

Cleanup struct dm_target by removing obvious comments and
adding comments on mandatory/optional handlers.

show more ...

sys/dev/disk/dm: Fix/refactor TAILQ_HEAD structure

Some minor fixes.

Initialize TAILQs in init() since they are removed and freed
in uninit(). Not doing it in init() works only when init() is
guara

sys/dev/disk/dm: Fix/refactor TAILQ_HEAD structure

Some minor fixes.

Initialize TAILQs in init() since they are removed and freed
in uninit(). Not doing it in init() works only when init() is
guaranteed to be called once.

show more ...

sys/dev/disk/dm: Simplify list eviction

Similar to 64c24ea.

sys/dev/disk/dm: Cleanups

Remove a space from
dm_table_entry_t * table_en,
struct buf * bp,
dm_dev_t * dmv,
etc

No binary change.

sys/dev/disk/dm: Remove unused prototype and wrong comments

sys/dev/disk/dm: Cleanups

sys/dev/disk/dm: Conform to style(9)

sys/dev/disk/dm: Make global dm locks static

These are all local to each file.

If ever needed by others, it should provide appropriate
interface instead of allowing access to raw lock variables.

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.

dm - sync_devs() on creation, add new dict entries

* call sync_devs() on device creation to ensure all devices are visible
in userland immediately after return from kernel.

* add some new, so

dm - sync_devs() on creation, add new dict entries

* call sync_devs() on device creation to ensure all devices are visible
in userland immediately after return from kernel.

* add some new, so far unusued, dict entries

* sneak in my copyright as I've rewritten large parts of dm. That way
at least everyone knows who to blame for broken stuff :)

show more ...

dm - add remove_all, refactor

* Refactor the dm dev creation and removal methods as to avoid
duplication and, as a bonus, do things properly.

* Rename foo_destroy to foo_uninit, because that's wh

dm - add remove_all, refactor

* Refactor the dm dev creation and removal methods as to avoid
duplication and, as a bonus, do things properly.

* Rename foo_destroy to foo_uninit, because that's what they really are,
uninit functions.

* Add an experimental 'remove_all' method

* Move atoi64 into device-mapper so that the striped target works
without loading the linear target.

show more ...

dm - undo my pointless moving of dm.h

* There was no need to move dm.h, we can just use <dev/disk/dm/dm.h>.

* And since we can do the above, we can also get rid of the strange
Makefile CFLAGS mag

dm - undo my pointless moving of dm.h

* There was no need to move dm.h, we can just use <dev/disk/dm/dm.h>.

* And since we can do the above, we can also get rid of the strange
Makefile CFLAGS magic I added.

* Also undo the removal on upgrade of /usr/include/dev/disk/dm/dm.h and
instead remove sys/dm.h

Reported-by: Sascha Wildner

show more ...

dm - Modularize it fully

* Move each of the targets (except error and zero) into a subdirectory
in targets/.

* Change the macro DM_TARGET_MODULE to also let the module depend on dm.

* Add a new

dm - Modularize it fully

* Move each of the targets (except error and zero) into a subdirectory
in targets/.

* Change the macro DM_TARGET_MODULE to also let the module depend on dm.

* Add a new macro DM_TARGET_BUILTIN, which must be used instead of
DM_TARGET_MODULE for targets that are compiled into the main dm.ko
instead of a separate module. Not doing this will prevent dm.ko from
unloading.

* Enable automatic loading of target modules if they aren't builtin or
loaded yet. Automatically loaded modules can be unloaded via kldunload
safely via a little hack (see source).

* NOTE: automatic loading doesn't always work. /boot must be mounted
already, so if you are planning on encrypting your swap or similar
stuff, you need to *EXPLICITLY* load dm_target_crypt.ko via the
loader.

* NOTE: PLEASE NOTE THE NOTE ABOVE!

* Fix a little issue with dm_target_crypt that would print "unloaded"
even if it wouldn't unload.

* Change the name of dm_target_stripe to dm_target_striped, since the
target is actually called "striped".

* Move dm.h to sys/sys/dm.h

* Get rid of files.dm, a leftover from the import

show more ...

dm - remove convoluted string comparison methods

dm - Major cleanup & module work

* Add module code to all the targets and get rid of the hackish global
target insertion.

* Clean up all sorts of dead code and crappy whitespaces. There isn't
m

dm - Major cleanup & module work

* Add module code to all the targets and get rid of the hackish global
target insertion.

* Clean up all sorts of dead code and crappy whitespaces. There isn't
much point in maintaining whitespaces just to have a small diff to
NetBSD since our diff is quite big now anyways.

show more ...

dm_target_crypt - use mpipe, add module magic

* Switch the kmallocs in the I/O path to using mpipe with a bare minimum
of two preallocated elements, for each read and write. This finally
allows

dm_target_crypt - use mpipe, add module magic

* Switch the kmallocs in the I/O path to using mpipe with a bare minimum
of two preallocated elements, for each read and write. This finally
allows for an encrypted swap without any issues with memory pressure.
It might also improve performance, but it is not the aim of the
commit.

* Add some module magic to dm and make use of it in dm_target_crypt.

* (temporarily) remove the old module magic.

show more ...

device mapper - implement dumping

* Implement dmdump and dump routines for the three main targets (linear,
stripe and crypt).

* The top-level dmpdump will call all the required dump() methods in

device mapper - implement dumping

* Implement dmdump and dump routines for the three main targets (linear,
stripe and crypt).

* The top-level dmpdump will call all the required dump() methods in the
targets just as it does with strategy() calls. The lower level
target-specific dump routines will then redirect (after processing,
etc) these requests to the underlying device's dump routines.

* This should provide quite reliable dumping even through device mapper,
although it is more error-prone than the equivalent dumping on normal
disks as there's a lot more going on behind the scenes.

show more ...

dm_target_crypt - Bump version to 1.6.0