Skip to content

Linux 6.12: fuse: bound the attribute timeout of an inode a DLM lock was taken on - #269

Merged
hbirth merged 1 commit into
DDNStorage:redfs-rhel10_0from
hbirth:redfs-rhel10_0
Oct 16, 2026
Merged

hbirth merged 1 commit into
DDNStorage:redfs-rhel10_0from
hbirth:redfs-rhel10_0

Conversation

@hbirth

@hbirth hbirth commented Oct 16, 2026

Copy link
Copy Markdown
Collaborator

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 and every later attr_valid to dlm_attr_timeout seconds, so a GETATTR is sent at least that often. Default 30s, module parameter, 0 keeps the server's timeout.

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 merged commit 4c3cedc into DDNStorage:redfs-rhel10_0 Oct 16, 2026
2 checks passed
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