summaryrefslogtreecommitdiff
path: root/WHATS_NEW_DM
Commit message (Collapse)AuthorAgeFilesLines
* post-releaseMarian Csontos2022-02-071-0/+3
|
* pre-releasev2_03_15Marian Csontos2022-02-071-2/+2
|
* libdm: unmangling UUID for DM_DEVICE_LISTZdenek Kabelac2021-12-201-0/+1
| | | | | Properly unmangle UUID if they are provided as result of DM_DEVICE_LIST ioctl on newer linux kernels.
* post-releaseMarian Csontos2021-10-201-0/+3
|
* pre-releasev2_03_14Marian Csontos2021-10-201-2/+2
|
* libdm: dmsetup measure support for IMAAlasdair G Kergon2021-09-231-0/+1
| | | | | | | Add support for DM_IMA_MEASUREMENT_FLAG with DM_TABLE_STATUS_CMD. This feature requires DM version 4.45 (5.15+ kernels)
* libdm: support DM_NAME_LIST_FLAGZdenek Kabelac2021-09-231-0/+1
| | | | | | | | | | | | | | | | | Kernel patch 8b638081bd4520f63db1defc660666ec5f65bc15 introduced support to return UUID in DM_LIST_DEVICES_CMD. Useful when asking for UUID of each device where the list could be now returned directly with NAME && UUID for each device. Returning UUID is done in backward-compatible way. There's one unused 32-bit word value after the event number. This patch sets the bit DM_NAME_LIST_FLAG_HAS_UUID if UUID is present and DM_NAME_LIST_FLAG_DOESNT_HAVE_UUID if it isn't (if none of these bits is set, then we have an old kernel that doesn't support returning UUIDs). The UUID is stored after this word. The 'next' value is updated to point after the UUID, so that old version of libdevmapper will skip the UUID without attempting to interpret it.
* libdm: enhance tracking of activated LVsZdenek Kabelac2021-09-131-0/+1
| | | | | | Existing mechanism was not able to trace root volume issue. Simplify the functionality by using simply using activated flag and trace the dtree in reverse order.
* cache: fix parentheses for migration_thresholdZdenek Kabelac2021-09-131-0/+1
| | | | | | | | | | | When generating table line for cache target line, the estimation of added arguments was incorrectly calculated as the evaluation order of "?" is made after "+". However the result was 'masked' by the Reported-by: Jian Cai jcai19
* post-releaseMarian Csontos2021-08-111-0/+3
|
* pre-releasev2_03_13Marian Csontos2021-08-111-2/+2
|
* post-releaseMarian Csontos2021-05-071-0/+3
|
* pre-releasev2_03_12Marian Csontos2021-05-071-2/+2
|
* WHATS_NEW: updatesZdenek Kabelac2021-04-121-0/+1
|
* WHATS_NEW: updatesZdenek Kabelac2021-04-061-0/+1
|
* all: fix typosSamanta Navarro2021-03-301-1/+1
|
* libdm: add dm_tree_node_add_thin_pool_target_v1Zdenek Kabelac2021-02-011-0/+1
| | | | Supports thin-pool without crop.
* post-releaseMarian Csontos2021-01-081-0/+3
|
* pre-releasev2_03_11Marian Csontos2021-01-081-2/+2
|
* dm: remove created devices on error pathZdenek Kabelac2020-10-191-0/+1
| | | | | | | | DM tree keeps track of created device while preloading a device tree. When fail occures during such preload, it will now try to remove all created and preloaded device. This makes it easier to maintain stacking of device, since we do not need to check in-depth for existance of all possible created devices during the failure.
* post-releaseMarian Csontos2020-08-091-0/+3
|
* pre-releasev2_03_10Marian Csontos2020-08-091-2/+2
|
* blkdeactivate: add support for VDO in blkdeactivate scriptPeter Rajnoha2020-04-091-0/+1
| | | | | | Make it possible to tear down VDO volumes with blkdeactivate if VDO is part of a device stack (and if VDO binary is installed). Also, support optional -o|--vdooptions configfile=file.
* post-releaseMarian Csontos2020-03-261-0/+3
|
* pre-releasev2_03_09Marian Csontos2020-03-261-2/+2
|
* WHATS_NEW_DM: updateZdenek Kabelac2020-03-051-0/+2
|
* post-releaseMarian Csontos2020-02-111-0/+3
|
* pre-releasev2_03_08Marian Csontos2020-02-111-1/+1
|
* libdm: support device RELOAD with maj:min and devname setZdenek Kabelac2019-12-101-0/+1
| | | | | | | | | | When devices are created - we were not giving meaning error messages when the failure happened on 'reload' part of creation. With this patch we are now able to report both name and major:minor. Enhancment is most visible with 'crypto' devices, which are using 'secure' memory erase bit.
* post-releaseMarian Csontos2019-11-301-0/+3
|
* pre-releasev2_03_07Marian Csontos2019-11-301-2/+2
|
* post-releaseMarian Csontos2019-10-231-0/+3
|
* pre-releasev2_03_06Marian Csontos2019-10-231-2/+2
|
* dm: fix compilation of dmsetupMarian Csontos2019-10-221-1/+1
| | | | | Fix: 889c88e9dab33195efc4dc0400a4b0aaa3383948 Use correct enum DM_DEVICE_GET_TARGET_VERSION.
* WHATS_NEW: updateZdenek Kabelac2019-10-041-0/+1
|
* dmsetup: debug printZdenek Kabelac2019-08-201-0/+1
| | | | | | | Udev debugging is a bit tricky, so to more easily pair cookie ID, which is the lowest 16 bit - print cookie as hexa number. This simplify pairing of processed cookies while the 'higher bit flags' are changed for the same cookie.
* exported_symbols: comment old symbolsZdenek Kabelac2019-08-091-0/+1
| | | | | | | | | | | | | | | Fix versioning for updated symbols dm_stats_create_region and dm_stats_create_region. Only the latest symbol should have global entry. Since I'm not sure what is currenlty the best option for old symbols - we added support for easy commenting of them (so we do not lose information when the symbol appeared for the first time.) Note: some old already deleted symbols should have been restored as comments.
* post-releaseMarian Csontos2019-06-151-0/+3
|
* pre-releasev2_03_05Marian Csontos2019-06-151-1/+1
|
* post-releaseMarian Csontos2019-06-101-0/+3
|
* pre-releasev2_03_04Marian Csontos2019-06-101-2/+2
|
* post-releaseMarian Csontos2019-06-071-1/+4
|
* pre-releasev2_03_03Marian Csontos2019-06-071-1/+5
|
* cache: support no_discard_passdownZdenek Kabelac2019-06-051-0/+1
| | | | | | | | | | | | | | | | | Recent kernel version from kernel commit: de7180ff908b2bc0342e832dbdaa9a5f1ecaa33a started to report in cache status line new flag: no_discard_passdown Whenever lvm spots unknown status it reports: Unknown feature in status: So add reconginzing this feature flag and also report this with 'lvs -o+kernel_discards' When no_discard_passdown is found in status 'nopassdown' gets reported for this field (roughly matching what we report for thin-pools).
* dm: migration_threshold for old linked toolsZdenek Kabelac2019-01-211-0/+1
| | | | | | Just like with precending lvm2 device_mapper patch, ensure that old users of libdm will also get fixed migration threshold for caches.
* libdm: use libdm headerZdenek Kabelac2018-12-141-0/+1
| | | | User libdm header file.
* libdm: print params only for ioctls using themZdenek Kabelac2018-11-171-0/+1
| | | | | | | When preparing ioctl buffer and flatting all parameters, add table parameters only to ioctl that do process them. Note: list of ioctl should be kept in sync with kernel code.
* libdm: add DM_DEVICE_ARM_POLLZdenek Kabelac2018-11-171-0/+1
| | | | Expose DM_DEVICE_ARM_POLL via standard API enum.
* libdm: do not add params for resume and removeZdenek Kabelac2018-11-171-0/+1
| | | | | | | | | | | | | | | | | | | DM_DEVICE_CREATE with table is doing several ioctl operations, however only some of then takes parameters. Since _create_and_load_v4() reused already existing dm task from DM_DEVICE_RELOAD it has also kept passing its table parameters to DM_DEVICE_RESUME ioctl - but this ioctl is supposed to not take any argument and thus there is no wiping of passed data - and since kernel returns buffer and shortens dmi->data_size accordingly, anything past returned data size remained uncleared in zfree() function. This has problem if the user used dm_task_secure_data (i.e. cryptsetup), as in this case binary expact secured data are erased from main memory after use, but they may have been left in place. This patch is also closing the possible hole for error path, which also reuse same dm task structure for DM_DEVICE_REMOVE.
* post-releaseMarian Csontos2018-10-311-0/+3
|
View Lorry Controller Status