kernel/linux.git/drivers/md/dm-delay.c, branch v4.17.1

dm: backfill missing calls to mutex_destroy()

2018-01-17T14:16:15+00:00

Signed-off-by: Mike Snitzer

md: Convert timers to use timer_setup()

2017-11-15T03:11:57+00:00

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Cc: Kent Overstreet Cc: Shaohua Li Cc: Alasdair Kergon Cc: Mike Snitzer Cc: dm-devel@redhat.com Cc: linux-bcache@vger.kernel.org Cc: linux-raid@vger.kernel.org Signed-off-by: Kees Cook Reviewed-by: Michael Lyle Reviewed-by: Mike Snitzer Signed-off-by: Jens Axboe

block: replace bi_bdev with a gendisk pointer and partitions index

2017-08-23T18:49:55+00:00

This way we don't need a block_device structure to submit I/O. The block_device has different life time rules from the gendisk and request_queue and is usually only available when the block device node is open. Other callers need to explicitly create one (e.g. the lightnvm passthrough code, or the new nvme multipathing code). For the actual I/O path all that we need is the gendisk, which exists once per block device. But given that the block layer also does partition remapping we additionally need a partition index, which is used for said remapping in generic_make_request. Note that all the block drivers generally want request_queue or sometimes the gendisk, so this removes a layer of indirection all over the stack. Signed-off-by: Christoph Hellwig Signed-off-by: Jens Axboe

dm: mark targets that pass integrity data

2017-04-24T16:04:32+00:00

A dm-crypt on dm-integrity device incorrectly advertises an integrity profile on the DM crypt device. It can be seen in the files "/sys/block/dm-*/integrity/*" that both dm-integrity and dm-crypt target advertise the integrity profile. That is incorrect, only the dm-integrity target should advertise the integrity profile. A general problem in DM is that if we have a DM device that depends on another device with an integrity profile, the upper device will always advertise the integrity profile, even when the target driver doesn't support handling integrity data. Most targets don't support integrity data, so we provide a whitelist of targets that support it (linear, delay and striped). The targets that support passing integrity data to the lower device are marked with the flag DM_TARGET_PASSES_INTEGRITY. The DM core will now advertise integrity data on a DM device only if all the targets support the integrity data. Signed-off-by: Mikulas Patocka Signed-off-by: Mike Snitzer

dm: rename target's per_bio_data_size to per_io_data_size

2016-02-23T03:34:37+00:00

Request-based DM will also make use of per_bio_data_size. Signed-off-by: Mike Snitzer

dm delay: document that offsets are specified in sectors

2015-10-31T23:06:05+00:00

Only delay params are mentioned in delay.txt. Mention offsets just like documents for linear and flakey do. Signed-off-by: Tomohiro Kusumi Signed-off-by: Mike Snitzer

dm delay: capitalize the start of an delay_ctr() error message

2015-10-31T23:06:04+00:00

All other error messages start capitalized. Signed-off-by: Tomohiro Kusumi Signed-off-by: Mike Snitzer

dm delay: Use DM_MAPIO macros instead of open-coded equivalents

2015-10-31T23:06:04+00:00

.map function of dm-delay returns return value of delay_bio(), hence it's supposed to return using a defined DM_MAPIO macro. Signed-off-by: Tomohiro Kusumi Acked-By: Mikulas Patocka Signed-off-by: Mike Snitzer

dm: do not override error code returned from dm_get_device()

2015-08-12T15:32:21+00:00

Some of the device mapper targets override the error code returned by dm_get_device() and return either -EINVAL or -ENXIO. There is nothing gained by this override. It is better to propagate the returned error code unchanged to caller. This work was motivated by hitting an issue where the underlying device was busy but -EINVAL was being returned. After this change we get -EBUSY instead and it is easier to figure out the problem. Signed-off-by: Vivek Goyal Signed-off-by: Mike Snitzer

dm delay: use msecs_to_jiffies for time conversion

2015-04-15T16:10:21+00:00

Converting milliseconds to jiffies by "val * HZ / 1000" is technically OK but msecs_to_jiffies(val) is the cleaner solution and handles all corner cases correctly. Signed-off-by: Nicholas Mc Guire Signed-off-by: Mike Snitzer