Skip to content

Conversation

@lucylq
Copy link
Contributor

@lucylq lucylq commented Nov 6, 2025

Summary:
Add safety checks to compute_slice, to ensure that we:

  1. Do not read outside of the src tensor bounds
  2. Do not write outside of the output tensor bounds

Differential Revision: D86433966

@pytorch-bot
Copy link

pytorch-bot bot commented Nov 6, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/15647

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures, 1 Cancelled Job, 2 Unrelated Failures

As of commit 0cdd555 with merge base 692825d (image):

NEW FAILURES - The following jobs have failed:

CANCELLED JOB - The following job was cancelled. Please retry:

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Nov 6, 2025
@meta-codesync
Copy link

meta-codesync bot commented Nov 6, 2025

@lucylq has exported this pull request. If you are a Meta employee, you can view the originating Diff in D86433966.

@github-actions
Copy link

github-actions bot commented Nov 6, 2025

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

lucylq added a commit to lucylq/executorch-1 that referenced this pull request Nov 6, 2025
Summary:

Add safety checks to compute_slice, to ensure that we:

1. Do not read outside of the src tensor bounds
2. Do not write outside of the output tensor bounds

Differential Revision: D86433966
lucylq added a commit to lucylq/executorch-1 that referenced this pull request Nov 6, 2025
Summary:

Add safety checks to compute_slice, to ensure that we:

1. Do not read outside of the src tensor bounds
2. Do not write outside of the output tensor bounds

Differential Revision: D86433966
@lucylq lucylq force-pushed the export-D86433966 branch 2 times, most recently from 33318db to 05695b6 Compare November 6, 2025 19:36
lucylq added a commit to lucylq/executorch-1 that referenced this pull request Nov 6, 2025
Summary:

Add safety checks to compute_slice, to ensure that we:

1. Do not read outside of the src tensor bounds
2. Do not write outside of the output tensor bounds

Also pass in KernelRuntimeContext to use ET_KERNEL_CHECK_MSG and make errors non-fatal.

Differential Revision: D86433966
Summary:

Add safety checks to compute_slice, to ensure that we:

1. Do not read outside of the src tensor bounds
2. Do not write outside of the output tensor bounds

Also pass in KernelRuntimeContext to use ET_KERNEL_CHECK_MSG and make errors non-fatal.

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

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant