Bug 790584 - Segfaults in error-handling within pycrypto
Segfaults in error-handling within pycrypto
Product: Fedora
Classification: Fedora
Component: python-crypto (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Paul Howarth
Fedora Extras Quality Assurance
Depends On:
Blocks: cpychecker
  Show dependency treegraph
Reported: 2012-02-14 16:30 EST by Dave Malcolm
Modified: 2012-02-28 05:56 EST (History)
3 users (show)

See Also:
Fixed In Version: python-crypto-2.5-2.fc17
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-02-28 05:56:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 934294 None None None Never

  None (edit)
Description Dave Malcolm 2012-02-14 16:30:23 EST
Description of problem:
I've been writing an experimental static analysis tool to detect bugs commonly occurring within C Python extension modules:

I ran the latest version of the tool (in git master; post 0.9) on python-crypto-2.5-1.fc17.src.rpm, and it reports various errors.

You can see a list of errors here, triaged into categories (from most significant to least significant):

Note that the top-most bug there is a false positive (reported for "Segfaults in normal paths" - "Crypto.Random" always has a "new" member, though the checker can't know that)

I believe that the five errors reported within "Segfaults within error-handling paths" are genuine crashers, which could be seen under low memory conditions.

(There may of course be other bugs in my checker tool)

Version-Release number of selected component (if applicable):

[1] http://fedoraproject.org/wiki/Features/StaticAnalysisOfPythonRefcounts
Comment 1 Dave Malcolm 2012-02-14 16:37:14 EST
[If this bug report is mystifying to you, let me know - I'm trying to iron out the wrinkles in the analysis tool]
Comment 2 Paul Howarth 2012-02-17 10:53:49 EST
I've reported this upstream:

Comment 3 Paul Howarth 2012-02-18 17:39:21 EST
I've included upstream's fixes for these issues in python-crypto-2.5-2 (built in Rawhide and building for F-17). Can you try re-running your checker on the new code?
Comment 4 Fedora Update System 2012-02-18 17:51:58 EST
python-crypto-2.5-2.fc17 has been submitted as an update for Fedora 17.
Comment 5 Fedora Update System 2012-02-18 23:36:42 EST
Package python-crypto-2.5-2.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-crypto-2.5-2.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Comment 6 Fedora Update System 2012-02-28 05:56:57 EST
python-crypto-2.5-2.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.