py/obj: Add new type flag to indicate subscr accepts slice-on-stack. #17736
+33
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Code size report: |
8b65d69 to
d54de76
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #17736 +/- ##
=======================================
Coverage 98.41% 98.41%
=======================================
Files 171 171
Lines 22210 22211 +1
=======================================
+ Hits 21857 21858 +1
Misses 353 353 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This was referenced Jul 22, 2025
|
This makes sense and seems worth spending a flag bit on. |
projectgus
approved these changes
Jul 23, 2025
The recently merged 5e9189d now allows temporary slices to be allocated on the C stack, which is much better than allocating them on the GC heap. Unfortunately there are cases where the C-allocated slice can escape and be retained as an object, which leads to crashes (because that object points to the C stack which now has other values on it). The fix here is to add a new `MP_TYPE_FLAG_SUBSCR_ALLOWS_STACK_SLICE`. Native types should set this flag if their subscr method is guaranteed not to hold on to a reference of the slice object. Fixes issue micropython#17733 (see also micropython#17723). Signed-off-by: Damien George <damien@micropython.org>
d54de76 to
49f5f42
Compare
Ah, thanks! Now fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The recently merged PR #12518 allowed temporary slices to be allocated on the C stack, which is much better than allocating them on the GC heap.
Unfortunately there are cases where the C-allocated slice can escape and be retained as an object, which leads to crashes (because that object points to the C stack which now has other values on it).
See #17723 and #17733.
The fix here is to add a new
MP_TYPE_FLAG_SUBSCR_ALLOWS_STACK_SLICE. Native types should set this flag if theirsubscrmethod is guaranteed not to hold on to a reference of the slice object.Testing
The existing tests pass. A new test is added to test the bugs reported in #17723 and #17733.
Trade-offs and Alternatives
The function
mp_obj_is_native_type()actually tests a type flag, so we replace the test of one flag with another flag. Thus the fix here should be no change in code size and no change in performance.We do use up another
MP_TYPE_FLAG_xxxbit, but there are still 5 left.Eventually more native types (eg tuple, list) can have this flag set, but I'll leave that for a follow-up PR.