Out-of-bounds accesses in operator execution

[lucylq]

Stack from ghstack (oldest at bottom):

• Integer overflow in HierarchicalAllocator::get_offset_address() #12699
• -> Out-of-bounds accesses in operator execution #12698
• Check for buffer overflow in prim_ops::et_copy_index() #12697

^

Test on top of D78676341

Differential Revision: D78702540

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• ghstack-mergeability-check and Check labels failing with 'Resource not accessible by integration'

❌ 2 New Failures

As of commit 1ef472d with merge base e4bc149 ():

NEW FAILURES - The following jobs have failed:

• Propose to merge ghstack orig PRs to main / Try to create a PR with ghstack /orig branch (gh)
  Process completed with exit code 1.
• pull / test-eval_llama-mmlu-linux / linux-job (gh)
  RuntimeError: Command docker exec -t aaf2a2d3051c0c9ac4629c45c9e150fb28bd64e19801617d0ebd0e29f1888361 /exec failed with exit code 1

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

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D78702540

[github-actions]

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.

[swolchok]

@lucylq did you want to close this one?