Home
last modified time | relevance | path

Searched refs:provided_data_sectors (Results 1 – 2 of 2) sorted by relevance

/linux/drivers/md/
H A Ddm-integrity.c76 __le64 provided_data_sectors; /* userspace uses this value */ member
203 sector_t provided_data_sectors; member
1914 if (unlikely(logical_sector + bio_sectors(bio) > ic->provided_data_sectors)) { in dm_integrity_check_limits()
1917 ic->provided_data_sectors); in dm_integrity_check_limits()
2837 if (unlikely(sec >= ic->provided_data_sectors)) { in do_journal_write()
2852 if (unlikely(sec2 >= ic->provided_data_sectors)) in do_journal_write()
3039 if (unlikely(range.logical_sector >= ic->provided_data_sectors)) { in integrity_recalc()
3041 block_bitmap_op(ic, ic->recalc_bitmap, 0, ic->provided_data_sectors, BITMAP_OP_CLEAR); in integrity_recalc()
3049 range.n_sectors = min((sector_t)recalc_sectors, ic->provided_data_sectors - range.logical_sector); in integrity_recalc()
3196 if (unlikely(range.logical_sector >= ic->provided_data_sectors)) in integrity_recalc_inline()
[all …]
/linux/Documentation/admin-guide/device-mapper/
H A Ddm-integrity.rst56 4. read the "provided_data_sectors" value from the superblock
58 "provided_data_sectors"
60 with the size "provided_data_sectors"