Skip to content

Conversation

@lorelei-sakai
Copy link
Member

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.

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.

Signed-off-by: Matthew Sakai <[email protected]>
@lorelei-sakai lorelei-sakai merged commit f2e2b77 into dm-vdo:main May 13, 2025
3 of 4 checks passed
@lorelei-sakai lorelei-sakai deleted the fix/pending-search-cleanup branch May 13, 2025 00:21
lorelei-sakai added a commit that referenced this pull request Jul 30, 2025
[VDO-5642][VDO-5644] dm vdo indexer: don't read request structure after enqueuing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants