RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1791525 - [RHEL-7 | x86_64] crash-ptdump-command test failed : ptdump: invalid size request: 0 type: "read page for write"
Summary: [RHEL-7 | x86_64] crash-ptdump-command test failed : ptdump: invalid size req...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: crash-ptdump-command
Version: 7.7
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: kdump-bugs
QA Contact: xiaoying yan
URL:
Whiteboard:
Depends On: 1786497
Blocks: 1788766 1824304
TreeView+ depends on / blocked
 
Reported: 2020-01-16 03:06 UTC by Yoko Oguma
Modified: 2020-09-29 19:48 UTC (History)
9 users (show)

Fixed In Version: crash-ptdump-command-1.0.3-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1786497
Environment:
Last Closed: 2020-09-29 19:48:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3899 0 None None None 2020-09-29 19:48:47 UTC

Comment 2 Dave Anderson 2020-01-27 20:01:18 UTC
A patch to address this issue has been posted upstream:

  [Crash-utility] Extensions: ptdump update v1.0.7
  https://www.redhat.com/archives/crash-utility/2020-January/msg00007.html

  Hi Dave,

  The attached file is updated extension module ptdump v1.0.7.
  Please replace old one in extension site [1] with this tarball.

  Changelog:
  - ptdump: fix build warning: warning: this ‘if’ clause does not guard
  - ptdump: fix failure: ptdump: invalid size request: 0 type: "read page for write" 
  - ptdump: fix heap memory and fd leak when fault happens

  md5sum:
  b548afa3c44b6e7f81bce020297a1572

  [1] http://people.redhat.com/anderson/extensions.html#PTDUMP

  --
  Thanks.
  HATAYAMA, Daisuke

Comment 3 Dave Anderson 2020-01-27 20:09:48 UTC
The Commit Policy Overview in http://pkgs.devel.redhat.com/rules.html indicates
that rhel-7.8 requires: (rhel-7.8.0 == + and blocker == +)

Or maybe it should be deferred to rhel-7.9?

Comment 9 RHEL Program Management 2020-02-04 03:19:56 UTC
Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.

Comment 20 errata-xmlrpc 2020-09-29 19:48:43 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (crash-ptdump-command bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3899


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