History log of /dflybsd-src/sys/dev/disk/dm/device-mapper.c (Results 26 – 50 of 58)
Revision Date Author Comments
# a3c6b8ec 01-Oct-2015 Tomohiro Kusumi <kusumi.tomohiro@gmail.com>

sys/dev/disk/dm: Add if(debug) conditional to kprintf in strategy()

There are 6 unconditional aprint_debug() in dm strategy which
means there are 6 if(debug) conditional kprintf() for each
dm mappin

sys/dev/disk/dm: Add if(debug) conditional to kprintf in strategy()

There are 6 unconditional aprint_debug() in dm strategy which
means there are 6 if(debug) conditional kprintf() for each
dm mapping entry.

Compilers may optimize (it doesn't on my env via buildkernel),
but add if(debug) outside these prints and use aprint_normal().

show more ...


# 78869e36 30-Sep-2015 Tomohiro Kusumi <kusumi.tomohiro@gmail.com>

sys/dev/disk/dm: Fix indentation and cleanups


# bbb13156 29-Sep-2015 Tomohiro Kusumi <kusumi.tomohiro@gmail.com>

sys/dev/disk/dm: Remove prototype of not existing function


# 2250180c 19-Aug-2013 Sascha Wildner <saw@online.de>

Another typo fixing round (in messages and manpages) across the tree.


# 3d089c23 05-Jan-2013 Sascha Wildner <saw@online.de>

kernel/dm: Remove some unused variables.

Also start using a previously unused variable in dm_target_crypt.


# 8062d810 24-May-2012 Sascha Wildner <saw@online.de>

kernel: Remove some bogus casts to the own type.


# c6bbf777 27-Feb-2012 Alex Hornung <ahornung@gmail.com>

disk - add flag to use underlying psize

* If the top (disk subsystem) psize fails, try again with the
underlying raw device psize if the DSO_RAWPSIZE flag is set for the
disk.

* This allows

disk - add flag to use underlying psize

* If the top (disk subsystem) psize fails, try again with the
underlying raw device psize if the DSO_RAWPSIZE flag is set for the
disk.

* This allows for disk devices and slices without a proper disklabel to
return a correct psize, which in turn allows the device to be used
for swap.

* Previously that behaviour was integrated with the DSO_DEVICEMAPPER
flag.

show more ...


# d1d6f4eb 16-Feb-2012 Sascha Wildner <saw@online.de>

kernel: Include <sys/ioccom.h> where ioctls are defined (part 2).

Some cases that I previously missed.


# ba2ce341 15-Jul-2011 Alex Hornung <ahornung@gmail.com>

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 ...


# 51292ec6 15-Jul-2011 Alex Hornung <ahornung@gmail.com>

dm - add message support (one-way)


# ba65987c 14-Jul-2011 Alex Hornung <ahornung@gmail.com>

dm - get rid of excessive locking and redundancy

* Just use dev->si_drv1 for the strategy, disk ioctl and dump as the
underlying device and 'dmv' is guaranteed not to go away. Keep the
locked

dm - get rid of excessive locking and redundancy

* Just use dev->si_drv1 for the strategy, disk ioctl and dump as the
underlying device and 'dmv' is guaranteed not to go away. Keep the
locked approach (dm_dev_lookup) for open, close, and mapper ioctls to
ensure that we never rip out any node that's still in use.

* This eliminates exclusive locking in the IO path, which should
improve performance.

show more ...


# 0ba7b1a4 14-Dec-2010 Sascha Wildner <saw@online.de>

dm(4): Fix kernel compilation with 'device dm' in the config.


# 9fada28a 13-Dec-2010 Alex Hornung <ahornung@gmail.com>

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 ...


# a84e173e 02-Dec-2010 Alex Hornung <ahornung@gmail.com>

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 ...


# 7115a22b 01-Dec-2010 Alex Hornung <ahornung@gmail.com>

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 ...


# b878986e 26-Nov-2010 Alex Hornung <ahornung@gmail.com>

dm - misc minor cleanup

* remove dead code, weird white spaces and fix comments.


# e8f83946 26-Nov-2010 Alex Hornung <ahornung@gmail.com>

dm - properly encapsulate disable_dev


# 5c411e8e 25-Nov-2010 Alex Hornung <ahornung@gmail.com>

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 ...


# 956c8d71 19-Nov-2010 Alex Hornung <ahornung@gmail.com>

dm - Disallow active vol removal; ret err of ioctl cmd

* Disallow the removal of volumes that are currently in use (determined
by whether they are open or not).

* Return the error of the actual i

dm - Disallow active vol removal; ret err of ioctl cmd

* Disallow the removal of volumes that are currently in use (determined
by whether they are open or not).

* Return the error of the actual ioctl command that was executed and not
of some prop copyout.

Reported-by: Sascha Wildner

show more ...


# db596036 04-Nov-2010 Alex Hornung <ahornung@gmail.com>

dm - adjust use of minor numbers to new reality

* Allocate (theoretical) minor numbers using the devfs_clone_bitmap
facility instead of an ever-increasing int64.

* Set the actual minor of the dm-

dm - adjust use of minor numbers to new reality

* Allocate (theoretical) minor numbers using the devfs_clone_bitmap
facility instead of an ever-increasing int64.

* Set the actual minor of the dm-specific device information to the
minor returned by the disk subsystem.

* Undo some of the dkunit() uses as they only covered very specific use
cases.

show more ...


# 3af01d56 12-Nov-2010 Alex Hornung <ahornung@gmail.com>

dm/disk - cleanup, add '.' between name and slices

* Clean up some dm debugging introduced earlier.

* Add a DSO_DEVICEMAPPER option that will cause the disk subsystem to
introduce a '.' between t

dm/disk - cleanup, add '.' between name and slices

* Clean up some dm debugging introduced earlier.

* Add a DSO_DEVICEMAPPER option that will cause the disk subsystem to
introduce a '.' between the base name and the slices (i.e. foo.s0
instead of foos0).

show more ...


# 3b48c3c1 11-Nov-2010 Alex Hornung <ahornung@gmail.com>

dm/nestbuf - Bind into devstat, clean up

* Bind dm into devstat via nestbufs.

* Clean up several dm changes.


# 08cba728 11-Nov-2010 Alex Hornung <ahornung@gmail.com>

dm - bind logical devices into the disk subsystem

* Bind logical dm devices into the disk subsystem so that they are more
flexible. This way they'll appear as regular disks, they'll be able to
h

dm - bind logical devices into the disk subsystem

* Bind logical dm devices into the disk subsystem so that they are more
flexible. This way they'll appear as regular disks, they'll be able to
have a disk scheduler and disklabels can be created on top of them.

show more ...


# 79b7159f 21-Oct-2010 Alex Hornung <ahornung@gmail.com>

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 ...


# 27d04cb3 20-Oct-2010 Alex Hornung <ahornung@gmail.com>

device-mapper - fix dmsize

* dmsize was returning the size instead of setting ap->a_result and
returning 0.


123