Red Hat Bugzilla – 2052848 – valgrind test failed on s390x only, /CoreOS/perl-XML-Parser/Regression/bz1658512-buffer-overwrite-in-parse_stream-with-wide-characters
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.
Description of problem:
there is a tes case :
/CoreOS/perl-XML-Parser/Regression/bz1658512-buffer-overwrite-in-parse_stream-with-wide-characters
which fails in s390x only. The rest of arch seems to be OK.
Version-Release number of selected component (if applicable):
rpm -q perl-XML-Parser valgrind
perl-XML-Parser-2.46-9.el9.s390x
valgrind-3.18.1-8.el9.s390x
How reproducible:
always
Steps to Reproduce:
1. /usr/bin/bkr workflow-tomorrow --task=/distribution/install/rhel-buildroot --method=http --setup=workarounds --setup=beakerlib --sleep=0 --task=/CoreOS/perl-XML-Parser/Regression/bz1658512-buffer-overwrite-in-parse_stream-with-wide-characters --reserve --distro=rhel9 --whiteboard=debug me"
Actual results:
https://beaker.engineering.redhat.com/jobs/6283788
Expected results:
no failure
Additional info:
log from machine:
[root@s390x-kvm-022 ~]# perl -CO -e 'print q{<root>} . qq{\x{010d}} x 2**16 . q{</root>}' | valgrind --error-exitcode=1 -- xpath -q -e '/foo'
==51883== Memcheck, a memory error detector
==51883== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==51883== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==51883== Command: /usr/bin/xpath -q -e /foo
==51883==
==51883== Conditional jump or move depends on uninitialised value(s)
==51883== at 0x4C38218: __memmem_arch13 (in /usr/lib64/libc.so.6)
==51883== by 0x49B5B0F: Perl_pp_require (in /usr/lib64/libperl.so.5.32.1)
==51883== by 0x4964611: Perl_runops_standard (in /usr/lib64/libperl.so.5.32.1)
==51883== by 0x48D6ECD: Perl_call_sv (in /usr/lib64/libperl.so.5.32.1)
==51883== by 0x48D7D6B: Perl_call_list (in /usr/lib64/libperl.so.5.32.1)
==51883== by 0x48C60F3: ??? (in /usr/lib64/libperl.so.5.32.1)
==51883== by 0x48C7931: Perl_newATTRSUB_x (in /usr/lib64/libperl.so.5.32.1)
==51883== by 0x48C84F7: Perl_utilize (in /usr/lib64/libperl.so.5.32.1)
==51883== by 0x4904F33: Perl_yyparse (in /usr/lib64/libperl.so.5.32.1)
==51883== by 0x49B3BA1: ??? (in /usr/lib64/libperl.so.5.32.1)
==51883== by 0x49B5439: Perl_pp_require (in /usr/lib64/libperl.so.5.32.1)
==51883== by 0x4964611: Perl_runops_standard (in /usr/lib64/libperl.so.5.32.1)
==51883==
==51883==
==51883== HEAP SUMMARY:
==51883== in use at exit: 6,902,770 bytes in 29,231 blocks
==51883== total heap usage: 86,523 allocs, 57,292 frees, 16,702,293 bytes allocated
==51883==
==51883== LEAK SUMMARY:
==51883== definitely lost: 23,039 bytes in 31 blocks
==51883== indirectly lost: 62,300 bytes in 30 blocks
==51883== possibly lost: 6,802,828 bytes in 29,130 blocks
==51883== still reachable: 14,603 bytes in 40 blocks
==51883== of which reachable via heuristic:
==51883== newarray : 29,288 bytes in 894 blocks
==51883== suppressed: 0 bytes in 0 blocks
==51883== Rerun with --leak-check=full to see details of leaked memory
==51883==
==51883== Use --track-origins=yes to see where uninitialised values come from
==51883== For lists of detected and suppressed errors, rerun with: -s
==51883== ERROR SUMMARY: 10 errors from 1 contexts (suppressed: 0 from 0)