- 04 Mar, 2024 28 commits
-
-
Mike Snitzer authored
Expose control over dm-vdo's log-level in terms of a module param. It can be read and written via /sys/module/dm_vdo/parameters/log_level. Signed-off-by:
Mike Snitzer <snitzer@kernel.org> Signed-off-by:
Ken Raeburn <raeburn@redhat.com> Signed-off-by:
Matthew Sakai <msakai@redhat.com>
-
Mike Snitzer authored
Also update target major version number. All info is (or will be) accessible through alternative interfaces (e.g. "dmsetup message", module params, etc). Signed-off-by:
-
Mike Snitzer authored
Most should be VDO_SUCCESS. But comparing the return from kstrtouint() with UDS_SUCCESS (happens to be 0) makes no sense. Signed-off-by:
-
Matthew Sakai authored
Update indexer uses of ASSERT and ASSERT_LOG_ONLY to VDO_ASSERT and VDO_ASSERT_LOG_ONLY, respectively. Remove ASSERT and ASSERT_LOG_ONLY. Also rename uds_assertion_failed to vdo_assertion_failed. Signed-off-by:
-
Mike Snitzer authored
Signed-off-by:
-
Mike Snitzer authored
Also rename ASSERT to VDO_ASSERT and ASSERT_LOG_ONLY to VDO_ASSERT_LOG_ONLY. But re-introduce ASSERT and ASSERT_LOG_ONLY as a placeholder for the benefit of dm-vdo/indexer. Signed-off-by:
-
Mike Snitzer authored
Signed-off-by:
-
Mike Snitzer authored
Update all callers to check for VDO_SUCCESS. Signed-off-by:
-
Mike Snitzer authored
Update all callers to check for VDO_SUCCESS (most already did). Also fix whitespace for update_mapping() parameters. Signed-off-by:
-
Mike Snitzer authored
VDO_SUCCESS and UDS_SUCCESS were used interchangably, update all callers of VDO's memory-alloc functions to consistently check for VDO_SUCCESS. Signed-off-by:
-
Mike Snitzer authored
Signed-off-by:
-
Matthew Sakai authored
Also define VDO_SUCCESS in a more central location, and rename error block constants for clarity. Signed-off-by:
-
Mike Snitzer authored
__vdo_do_allocation shouldn't be used outside of memory-alloc.h, so add hidden prefix. Also, tabify the vdo_allocate_extended macro. Signed-off-by:
-
Mike Snitzer authored
Signed-off-by:
-
Bruce Johnston authored
Signed-off-by:
Bruce Johnston <bjohnsto@redhat.com> Signed-off-by:
-
Matthew Sakai authored
Signed-off-by:
-
Matthew Sakai authored
Update outdated comments referring to separate VDO and UDS modules. Signed-off-by:
-
Matthew Sakai authored
Signed-off-by:
-
Jiapeng Chong authored
No functional modification involved. Reported-by:
Abaci Robot <abaci@linux.alibaba.com> Signed-off-by:
Jiapeng Chong <jiapeng.chong@linux.alibaba.com> Signed-off-by:
-
Mike Snitzer authored
The goal is to assist high-level understanding of which code is conceptually specific to VDO's indexer. Signed-off-by:
-
Matthew Sakai authored
Signed-off-by:
-
Chung Chung authored
Ignore scnprintf return status since it is not necessary. Change write_* functions type from int to void since we no longer return any result. Also, clean up any code that checks or uses any scnprintf return results. Check uds_allocate return code which was previous ignored, return and log error when uds_allocate failed. Reported-by:
Dan Carpenter <dan.carpenter@linaro.org> Signed-off-by:
Chung Chung <cchung@redhat.com> Signed-off-by:
-
Mike Snitzer authored
Reported when building on loongarch. Reported-by:
Randy Dunlap <rdunlap@infradead.org> Signed-off-by:
-
Mike Snitzer authored
Must mutex_lock after dm_bufio_read, before dm_bufio_read error handling, otherwise process_entry error path will return without volume->read_threads_mutex held. This fixes potential double mutex_unlock. Reported-by:
Susan LeGendre-McGhee <slegendr@redhat.com> Signed-off-by:
-
Mike Snitzer authored
Otherwise, error path could result in allocate_flush's subsequent check for flush being non-NULL leading to false positive. Reported-by:
-
Dan Carpenter authored
This is a duplicate check so it can't be true. Delete it. Signed-off-by:
-
Mike Snitzer authored
Signed-off-by:
-
Susan LeGendre-McGhee authored
Signed-off-by:
-
- 01 Mar, 2024 12 commits
-
-
Mike Snitzer authored
Also moved vdo_init()'s call to vdo_initialize_thread_device_registry next to other registry initialization. Signed-off-by:
-
Mike Snitzer authored
Otherwise, uds_ prefix is misleading (vdo_ is the new catch-all for code that is used by vdo-only or _both_ vdo and the indexer code). Signed-off-by:
-
Mike Snitzer authored
Signed-off-by:
-
Mike Snitzer authored
Change thread function prefix from "uds_" to "vdo_" and fix vdo_join_threads() to return void. Signed-off-by:
-
Mike Snitzer authored
Just use mutex_init, mutex_lock and mutex_unlock. Signed-off-by:
-
Mike Snitzer authored
Only used by indexer components. Also return void from uds_init_cond(), remove uds_destroy_cond(), and fix up all callers. Signed-off-by:
-
Mike Snitzer authored
Further cleanup is needed for thread-utils interfaces given many functions should return void or be removed entirely because they amount to obfuscation via wrappers. Signed-off-by:
-
Mike Snitzer authored
Also remove unnecessary include from funnel-queue.c. Signed-off-by:
-
Mike Snitzer authored
Signed-off-by:
-
Mike Snitzer authored
Rename 'barrier' to 'threads_barrier', remove useless uds_destroy_barrier(), return void from remaining methods and clean up uds_make_sparse_cache() accordingly. Also remove uds_ prefix from the 2 remaining threads_barrier functions. Signed-off-by:
-
Mike Snitzer authored
The sparse-cache is the only user of the 'barrier' data structure, so just move it private to it. Signed-off-by:
-
Mike Snitzer authored
The implementation of thread 'barrier' data structure does not require overdone private semaphore wrappers. Also rename the barrier structure's 'mutex' member (a semaphore) to 'lock'. Signed-off-by:
-
