Skip to content

fuse: handle U64_MAX correctly in DLM locked range index#146

Open
hbirth wants to merge 1 commit into
DDNStorage:redfs-ubuntu-noble-6.8.0-58.60from
hbirth:redfs-ubuntu-noble-6.8.0-58.60
Open

fuse: handle U64_MAX correctly in DLM locked range index#146
hbirth wants to merge 1 commit into
DDNStorage:redfs-ubuntu-noble-6.8.0-58.60from
hbirth:redfs-ubuntu-noble-6.8.0-58.60

Conversation

@hbirth
Copy link
Copy Markdown
Collaborator

@hbirth hbirth commented Apr 22, 2026

When merging and checking overlap U64_MAX was not handled this will create problems on multiple DLM results that cover the whole range.

Add a fast path for adding and checking locked ranges when the whole range is covered.

@hbirth hbirth force-pushed the redfs-ubuntu-noble-6.8.0-58.60 branch 2 times, most recently from 963c63f to 5126d9a Compare April 23, 2026 09:08
Comment thread fs/fuse/fuse_dlm_cache.c Outdated
@hbirth hbirth force-pushed the redfs-ubuntu-noble-6.8.0-58.60 branch 2 times, most recently from bb2afd4 to 8fa4c8a Compare April 28, 2026 13:30
When merging and checking overlap U64_MAX was not handled
this will create problems on multiple DLM results that cover
the whole range.

Add a fast path for adding and checking locked ranges when
the whole range is covered.

Refactor dlm range handling to make it more readable.

Signed-off-by: Horst Birthelmer <hbirthelmer@ddn.com>
@hbirth hbirth force-pushed the redfs-ubuntu-noble-6.8.0-58.60 branch from 8fa4c8a to a31c2ee Compare May 15, 2026 10:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants