Skip to content

Linux 6.8: bind attribute timeout to DLM locking - #271

Merged
hbirth merged 2 commits into
DDNStorage:redfs-ubuntu-noble-6.8.0-58.60from
hbirth:redfs-ubuntu-noble-6.8.0-58.60
Oct 16, 2026
Merged

hbirth merged 2 commits into
DDNStorage:redfs-ubuntu-noble-6.8.0-58.60from
hbirth:redfs-ubuntu-noble-6.8.0-58.60

Conversation

@hbirth

@hbirth hbirth commented Oct 16, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

fuse_reverse_inval_inode() ignored the result of
invalidate_inode_pages2_range(), so folios left in the page cache after a
notify went unnoticed. Log a rate-limited warning when the invalidate
fails, and when the write in fuse_launder_folio() fails.
Under DLM the server's attr_valid can keep the attributes of a locked
inode valid indefinitely. Once a DLM lock was taken on an inode, cap
its i_time to dlm_attr_timeout seconds so a GETATTR goes out at most
that long after the lock. The first attribute reply from the server
after the lock ends the bound; a reply to a request sent before it is
discarded by bumping attr_version. Default 30s, module parameter, 0
keeps the server's timeout.

Signed-off-by: Horst Birthelmer <hbirthelmer@ddn.com>
@hbirth
hbirth force-pushed the redfs-ubuntu-noble-6.8.0-58.60 branch from 71f87e9 to e6db99c Compare October 16, 2026 12:07
@hbirth
hbirth merged commit 6c84e67 into DDNStorage:redfs-ubuntu-noble-6.8.0-58.60 Oct 16, 2026
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.

1 participant