Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 828513[details]
Full test log
Description of problem:
=== full diff out/out.bad ===
--- /dev/fd/63 2013-11-15 09:09:51.054274564 -0500
+++ results/xfs/302.out.bad 2013-11-15 09:09:48.920390607 -0500
@@ -1,2 +1,5 @@
QA output created by 302
Silence is golden.
+./tests/xfs/302: line 66: 1454 Segmentation fault $XFSRESTORE_PROG -F -f $tmp.stream1 -f $tmp.stream2 $restore_dir >> $seqres.full 2>&1
+restore failed
+(see /var/lib/xfstests/results//xfs/302.full for details)
And dmesg says
[10415.908023] xfsrestore[1456]: segfault at 20 ip 0000000000425ccd sp 00007feda23894e0 error 4 in xfsrestore[400000+53000]
Version-Release number of selected component (if applicable):
xfsdump-3.1.3-1.el7
How reproducible:
always
Steps to Reproduce:
1. check xfs/302 on xfs
2.
3.
Actual results:
test fails
Expected results:
test passes
Additional info:
Should be fixed by:
commit 1162bdbcff77ed2341f0a9294db76df80f2f36a3
Author: Eric Sandeen <sandeen>
Date: Tue Oct 8 22:05:54 2013 +0000
xfsdump: avoid segfault in partial_reg() in error case
I'll get that & related patches into the build, thanks.
-Eric
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Created attachment 828513 [details] Full test log Description of problem: === full diff out/out.bad === --- /dev/fd/63 2013-11-15 09:09:51.054274564 -0500 +++ results/xfs/302.out.bad 2013-11-15 09:09:48.920390607 -0500 @@ -1,2 +1,5 @@ QA output created by 302 Silence is golden. +./tests/xfs/302: line 66: 1454 Segmentation fault $XFSRESTORE_PROG -F -f $tmp.stream1 -f $tmp.stream2 $restore_dir >> $seqres.full 2>&1 +restore failed +(see /var/lib/xfstests/results//xfs/302.full for details) And dmesg says [10415.908023] xfsrestore[1456]: segfault at 20 ip 0000000000425ccd sp 00007feda23894e0 error 4 in xfsrestore[400000+53000] Version-Release number of selected component (if applicable): xfsdump-3.1.3-1.el7 How reproducible: always Steps to Reproduce: 1. check xfs/302 on xfs 2. 3. Actual results: test fails Expected results: test passes Additional info: