Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

seqlock: Use WRITE_ONCE() when updating sequence #8265

Closed

Conversation

danobi
Copy link
Contributor

@danobi danobi commented Dec 17, 2024

sequence is a concurrently accessed shared variable on the reader side. Therefore, it needs to be wrapped in WRITE_ONCE() in order to prevent unwanted compiler optimizations like store tearing.

Kernel Patches Daemon and others added 2 commits December 17, 2024 11:06
`sequence` is a concurrently accessed shared variable on the reader
side. Therefore, it needs to be wrapped in WRITE_ONCE() in order to
prevent unwanted compiler optimizations like store tearing.
@kernel-patches-daemon-bpf kernel-patches-daemon-bpf bot force-pushed the bpf-next_base branch 8 times, most recently from 0cdd956 to b0c73ce Compare December 23, 2024 21:31
@kernel-patches-daemon-bpf
Copy link

Automatically cleaning up stale PR; feel free to reopen if needed

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