Skip to content

[3.7] bpo-1621: Avoid signed integer overflow in set_table_resize(). (GH-9059) #9198

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

Merged
merged 1 commit into from
Oct 19, 2018

Conversation

miss-islington
Copy link
Contributor

Address a C undefined behavior signed integer overflow issue in set object table resizing. Our -fwrapv compiler flag and practical reasons why sets are unlikely to get this large should mean this was never an issue but it was incorrect code that generates code analysis warnings.

https://bugs.python.org/issue1621

(cherry picked from commit 6c7d67c)

Co-authored-by: Sergey Fedoseev [email protected]

…nGH-9059)

Address a C undefined behavior signed integer overflow issue in set object table resizing.  Our -fwrapv compiler flag and practical reasons why sets are unlikely to get this large should mean this was never an issue but it was incorrect code that generates code analysis warnings.

<!-- issue-number: [bpo-1621](https://www.bugs.python.org/issue1621) -->
https://bugs.python.org/issue1621
<!-- /issue-number -->
(cherry picked from commit 6c7d67c)

Co-authored-by: Sergey Fedoseev <[email protected]>
@miss-islington
Copy link
Contributor Author

@sir-sigurd: Status check is done, and it's a success ✅ .

@ned-deily
Copy link
Member

@gpshead Is this ready to merge for 3.7?

@gpshead
Copy link
Member

gpshead commented Oct 7, 2018

Yes, though I'd wait until after you do the 3.7.1 release. No need for this to go in during an rc.

@vstinner vstinner merged commit 6665802 into python:3.7 Oct 19, 2018
@miss-islington miss-islington deleted the backport-6c7d67c-3.7 branch October 19, 2018 22:50
@vstinner
Copy link
Member

This backport is sitting for weeks. It has been properly validated by our buildbot fleet (on the master branch) and everything is fine. So I'm confident that it's safe for Python 3.7. I just merged the 3.6 backport as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants