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

Fix data race on prefetcher. #17678

Closed
wants to merge 1 commit into from
Closed

Conversation

tjgq
Copy link
Contributor

@tjgq tjgq commented Mar 7, 2023

Individual file prefetches within a single prefetchFiles() can race against each other, so they must synchronize when writing to the DirectoryContext.

@tjgq tjgq marked this pull request as ready for review March 7, 2023 15:46
@tjgq tjgq requested a review from a team as a code owner March 7, 2023 15:46
@tjgq tjgq requested a review from coeuvre March 7, 2023 15:46
@sgowroji sgowroji added the team-Remote-Exec Issues and PRs for the Execution (Remote) team label Mar 7, 2023
@brentleyjones
Copy link
Contributor

Should this land in 6.2 as well (asking more if it's broken in 6.x)?

@tjgq
Copy link
Contributor Author

tjgq commented Mar 7, 2023

Should this land in 6.2 as well (asking more if it's broken in 6.x)?

Yes, most definitely. (Note: we need to patch other changes first, most importantly 52deefe.)

@bazel-io fork 6.2.0

@ShreeM01
Copy link
Contributor

ShreeM01 commented Mar 7, 2023

@bazel-io fork 6.2.0

Individual file prefetches within a single prefetchFiles() can race against
each other, so they must synchronize when writing to the DirectoryContext.
@copybara-service copybara-service bot closed this in e0cdace Mar 8, 2023
ShreeM01 pushed a commit to ShreeM01/bazel that referenced this pull request Mar 10, 2023
Individual file prefetches within a single prefetchFiles() can race against each other, so they must synchronize when writing to the DirectoryContext.

Closes bazelbuild#17678.

PiperOrigin-RevId: 515024483
Change-Id: Ic8097979d06ab143b4d63f5e90f871f8cbf83959
tjgq added a commit to tjgq/bazel that referenced this pull request Mar 11, 2023
Individual file prefetches within a single prefetchFiles() can race against each other, so they must synchronize when writing to the DirectoryContext.

Closes bazelbuild#17678.

PiperOrigin-RevId: 515024483
Change-Id: Ic8097979d06ab143b4d63f5e90f871f8cbf83959
ShreeM01 added a commit that referenced this pull request Mar 13, 2023
Individual file prefetches within a single prefetchFiles() can race against each other, so they must synchronize when writing to the DirectoryContext.

Closes #17678.

PiperOrigin-RevId: 515024483
Change-Id: Ic8097979d06ab143b4d63f5e90f871f8cbf83959

Co-authored-by: kshyanashree <109167932+kshyanashree@users.noreply.github.com>
fweikert pushed a commit that referenced this pull request Mar 17, 2023
Individual file prefetches within a single prefetchFiles() can race against each other, so they must synchronize when writing to the DirectoryContext.

Closes #17678.

PiperOrigin-RevId: 515024483
Change-Id: Ic8097979d06ab143b4d63f5e90f871f8cbf83959
fweikert pushed a commit to fweikert/bazel that referenced this pull request May 25, 2023
Individual file prefetches within a single prefetchFiles() can race against each other, so they must synchronize when writing to the DirectoryContext.

Closes bazelbuild#17678.

PiperOrigin-RevId: 515024483
Change-Id: Ic8097979d06ab143b4d63f5e90f871f8cbf83959
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Remote-Exec Issues and PRs for the Execution (Remote) team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants