Bug 483396 - Crash when accessing hdr[rpm.RPMTAG_FSNAMES] twice in python
Crash when accessing hdr[rpm.RPMTAG_FSNAMES] twice in python
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Panu Matilainen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-01-31 11:45 EST by Ville Skyttä
Modified: 2009-07-15 04:19 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-15 04:19:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
gdb backtrace (7.88 KB, text/plain)
2009-01-31 11:45 EST, Ville Skyttä
no flags Details
Don't free data from RPMTAG_FSNAMES (373 bytes, patch)
2009-02-01 06:05 EST, Panu Matilainen
no flags Details | Diff

  None (edit)
Description Ville Skyttä 2009-01-31 11:45:54 EST
Created attachment 330526 [details]
gdb backtrace

F-9 x86_64

When accessing hdr[rpm.RPMTAG_FSNAMES] twice in Python, I get a crash.  Backtrace attached, reproducer:

import rpm
ts = rpm.TransactionSet()
mi = ts.dbMatch("name", "rpm")
for hdr in mi:
    foo = hdr[rpm.RPMTAG_FSNAMES]
    foo = hdr[rpm.RPMTAG_FSNAMES] # crash
Comment 1 Panu Matilainen 2009-02-01 06:05:09 EST
Created attachment 330545 [details]
Don't free data from RPMTAG_FSNAMES

Heh, this is probably a pretty ancient bug. RPMTAG_FSNAMES is the only string array type tag in rpm whose data must not be freed, but the python bindings assume all string arrays need freeing. The attached patch should fix but can't test right now.

Rpm 4.6 and later is not affected as the data returned from headers and extensions always contains information if the data needs freeing or not so there's no need for callers to "know" details like this.
Comment 2 Bug Zapper 2009-06-09 23:31:33 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Bug Zapper 2009-07-15 04:19:16 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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