Skip to content

serf: protect field access with lock to avoid potential data race #691

Description

@yanke-xu

I found a potential data race based on the code analysis. For example, there are two confilicting operations on the field "EventLTime", where the read operation at: serf/delegate.go:223, and the write operation which is protected by the eventLock at: serf/delegate.go:264. Similar to preventing write conflicts on line 264, the two operations may cause a data race.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions