kernel/git/stable/linux.git/drivers/md/dm-vdo/indexer, branch master

dm vdo indexer: embed geometry in parent structures

2026-07-28T12:34:47+00:00

Embed struct index_geometry in struct uds_configuration and struct volume directly, eliminating the need to allocate (and free) the geometry separately. Signed-off-by: corwin Signed-off-by: Matthew Sakai Signed-off-by: Mikulas Patocka

dm vdo indexer: simplify sub-index parameter calculations

2026-07-28T12:32:35+00:00

Pull the calculations from split_config() into compute_volume_sub_index_parameters(). For sparse indexes, this eliminates the duplication of both the configs and geometries in favor of merely having 2 sub_index_parameters structures. Also expand the sub_index_parameters structure to include the small number of fields its users rely on from both the config and the geometry. Signed-off-by: corwin Signed-off-by: Matthew Sakai Signed-off-by: Mikulas Patocka

dm vdo: use get_random_u32() where appropriate

2026-05-04T12:33:42+00:00

Use the typed random integer helpers instead of get_random_bytes() when filling a single integer variable. The helpers return the value directly, require no pointer or size argument, and better express intent. Signed-off-by: David Carlier Reviewed-by: Matthew Sakai Signed-off-by: Mikulas Patocka

dm vdo: add geometry block initialization to encodings.c

2026-03-26T17:17:31+00:00

Add vdo_initialize_volume_geometry() to populate the geometry block, computing the space required for the two main regions on disk. Add uds_compute_index_size() to calculate the space required for the UDS indexer from the UDS configuration. Signed-off-by: Bruce Johnston Reviewed-by: Matthew Sakai Signed-off-by: Mikulas Patocka

dm vdo: add __counted_by attribute to a number of structures

2026-03-02T16:03:37+00:00

This attribute allows the compiler to refine compile-time diagnostics and run-time sanitizer features with information about the size of the flexible arrays. Signed-off-by: Ken Raeburn Signed-off-by: Mikulas Patocka

dm vdo: remove redundant TYPE argument from vdo_allocate macro

2026-03-02T16:03:28+00:00

We can infer the type needed from the supplied pointer argument. A couple invocation sites needed fixing to supply the proper type of pointer. Use overflow.h's size_mul, and we can remove the __vdo_do_allocation wrapper which did the same overflow check. Signed-off-by: Ken Raeburn Signed-off-by: Mikulas Patocka

dm vdo: update vdo_allocate_extended to take a field name, no types

2026-03-02T16:03:18+00:00

All of VDO's "extended" allocations use a flexible array field at the end of the allocated structure. We can infer the struct type from the supplied pointer. Replacing the array field type with the field name lets us use struct_size from overflow.h to compute the size instead of the local __vdo_do_allocation version. One allocation of bio structures doesn't conform to this pattern, since the removal of bi_inline_vecs; directly compute the total size for that case. Signed-off-by: Ken Raeburn Signed-off-by: Mikulas Patocka

dm vdo indexer: validate saved zone count

2026-03-02T15:37:43+00:00

Verify that the loaded zone count is in the valid range before using it as a loop iterator. Signed-off-by: Matthew Sakai Signed-off-by: Mikulas Patocka

dm vdo: return error on corrupted metadata in start_restoring_volume functions

2025-09-23T08:49:45+00:00

The return values of VDO_ASSERT calls that validate metadata are not acted upon. Return UDS_CORRUPT_DATA in case of an error. Found by Linux Verification Center (linuxtesting.org) with SVACE. Fixes: a4eb7e255517 ("dm vdo: implement the volume index") Signed-off-by: Ivan Abramov Reviewed-by: Matthew Sakai Signed-off-by: Mikulas Patocka

dm vdo indexer: don't read request structure after enqueuing

2025-05-15T13:54:47+00:00

The function get_volume_page_protected may place a request on a queue for another thread to process asynchronously. When this happens, the volume should not read the request from the original thread. This can not currently cause problems, due to the way request processing is handled, but it is not safe in general. Reviewed-by: Ken Raeburn Signed-off-by: Matthew Sakai Signed-off-by: Mikulas Patocka