Skip to content

checklocks: guard in-memory xattrs - #14309

Closed
tamird wants to merge 1 commit into
google:masterfrom
tamird:checklocks-memxattr
Closed

checklocks: guard in-memory xattrs#14309
tamird wants to merge 1 commit into
google:masterfrom
tamird:checklocks-memxattr

Conversation

@tamird

@tamird tamird commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Enforce the existing mutex contract for the xattr map, including raw serialization accessors. RawXattrs continues to return a detached copy.

Assisted-by: Codex

@tamird

tamird commented Aug 22, 2026

Copy link
Copy Markdown
Contributor Author

r? @shailend-g Could you review the existing xattr-map mutex contract and detached serialization copies?

Focused local Bazel checks passed. Upstream checks have not reported yet.

Assisted-by: Codex

Enforce the existing mutex contract for the xattr map, including raw
serialization accessors. RawXattrs returns a detached copy, while
SetRawXattrs takes ownership of its input map. Document that caller
boundary and the map aliases that checklocks cannot track.

Assisted-by: Codex
@tamird
tamird force-pushed the checklocks-memxattr branch from a34660a to 64dbd21 Compare August 22, 2026 16:19
@tamird

tamird commented Aug 23, 2026

Copy link
Copy Markdown
Contributor Author

Closing in favor of consolidated #14343. The expanded replacement commits are prepared locally; the replacement branch has not been pushed yet.

Assisted-by: Codex

@tamird tamird closed this Aug 23, 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