Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

[core][cgraph] Fix illegal memory access of cgraph when used in PP#51734

Merged
edoakes merged 5 commits intoray-project:masterfromruisearch42:fix_ima
Mar 28, 2025

Conversation

ruisearch42
Copy link
Contributor

@ruisearch42ruisearch42 commentedMar 27, 2025
edited
Loading

Why are these changes needed?

This fixes the illegal memory access bug reported in#51596

The culprit PR is#51305
This PR technically just manually reverts#51305 because it's hard to simplygit revert that commit, because we now enforce that there are no core->air dependencies in CI. See#51699

This PR simply reverts to the original logic before#51305 , and makes code copy as needed. We wanted to first get the bug mitigated, and then follow up to simplify and tailor the logic ofutils.get_cuda_devices(), as it can be tricky.

Related issue number

Closes#51596

Checks

Verified that itfixes#51596

  • I've signed off every commit(by using the -s flag, i.e.,git commit -s) in this PR.
  • I've runscripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed forhttps://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it indoc/source/tune/api/ under the
      corresponding.rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures athttps://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@ruisearch42ruisearch42 added the goadd ONLY when ready to merge, run all tests labelMar 27, 2025
@edoakes
Copy link
Collaborator

What's the behavior difference here?

@ruisearch42ruisearch42 requested a review froma team as acode ownerMarch 27, 2025 15:37
@ruisearch42
Copy link
ContributorAuthor

What's the behavior difference here?

After this revert, the illegal memory access reported in#51596 is fixed.

Signed-off-by: Rui Qiao <ruisearch42@gmail.com>
Signed-off-by: Rui Qiao <ruisearch42@gmail.com>
Signed-off-by: Rui Qiao <ruisearch42@gmail.com>
@edoakes
Copy link
Collaborator

What's the behavior difference here?

After this revert, the illegal memory access reported in#51596 is fixed.

Yes, but why is the illegal memory access fixed? What is the meaningful behavior difference that was introduced in that PR?

@ruisearch42
Copy link
ContributorAuthor

Yes, but why is the illegal memory access fixed? What is the meaningful behavior difference that was introduced in that PR?

Discussed offline. The goal of this PR is revert and mitigation, I will follow up with further investigation and clean up the code.

@edoakesedoakes merged commit98d217e intoray-project:masterMar 28, 2025
5 checks passed
pavelkushtia pushed a commit to pavelkushtia/ray that referenced this pull requestApr 6, 2025
…ay-project#51734)This fixes the illegal memory access bug reported inray-project#51596The culprit PR isray-project#51305This PR technically just manually revertsray-project#51305 because it's hard tosimply `git revert` that commit, because we now enforce that there areno core->air dependencies in CI. Seeray-project#51699This PR simply reverts to the original logic beforeray-project#51305 , and makescode copy as needed. We wanted to first get the bug mitigated, and thenfollow up to simplify and tailor the logic of`utils.get_cuda_devices()`, as it can be tricky.## Related issue numberClosesray-project#51596---------Signed-off-by: Rui Qiao <ruisearch42@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@edoakesedoakesedoakes approved these changes

Assignees

@edoakesedoakes

Labels
goadd ONLY when ready to merge, run all tests
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[CG, Core] Illegal memory access with Ray 2.44 and vLLM v1 pipeline parallelism
2 participants
@ruisearch42@edoakes

[8]ページ先頭

©2009-2025 Movatter.jp