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.
DescriptionKaushik Banerjee
2014-09-09 08:47:47 UTC
Created attachment 935587[details]
valgrind log
Description of problem:
While troubleshooting failures in sssd via valgrind, instead I saw lot of errors related to prelink
See the attached valgrind log
==4820== Conditional jump or move depends on uninitialised value(s)
==4820== at 0x8007A108: free (in /usr/sbin/prelink)
==4820== by 0x8004C183: selinux_raw_to_trans_context (in /usr/sbin/prelink)
==4820== by 0x8004AD61: getfilecon (in /usr/sbin/prelink)
==4820== by 0x8001EDB9: set_security_context (dso.c:1793)
==4820== by 0x8002023B: update_dso (dso.c:1907)
==4820== by 0x80010E85: main (main.c:445)
Version-Release number of selected component (if applicable):
# rpm -q prelink
prelink-0.4.6-3.1.el6_4.s390x
How reproducible:
NA
Steps to Reproduce:
1. Added the following line in /etc/sssd/sssd.conf to test for a login failure:
command = valgrind -v --leak-check=full --trace-children=yes --show-reachable=yes --log-file=/var/log/sssd/valgrind_LDAP_%p.log /usr/libexec/sssd/sssd_be --domain LDAP --debug-to-files
2.
3.
Actual results:
Expected results:
Additional info:
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux. We've carefully evaluated the request, but are unable to include it in a future release as Red Hat Enterprise Linux 6 moves towards production phase 2[*]
To request that Red Hat re-consider this request, please re-open the bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.
[*] https://access.redhat.com/support/policy/updates/errata
Created attachment 935587 [details] valgrind log Description of problem: While troubleshooting failures in sssd via valgrind, instead I saw lot of errors related to prelink See the attached valgrind log ==4820== Conditional jump or move depends on uninitialised value(s) ==4820== at 0x8007A108: free (in /usr/sbin/prelink) ==4820== by 0x8004C183: selinux_raw_to_trans_context (in /usr/sbin/prelink) ==4820== by 0x8004AD61: getfilecon (in /usr/sbin/prelink) ==4820== by 0x8001EDB9: set_security_context (dso.c:1793) ==4820== by 0x8002023B: update_dso (dso.c:1907) ==4820== by 0x80010E85: main (main.c:445) Version-Release number of selected component (if applicable): # rpm -q prelink prelink-0.4.6-3.1.el6_4.s390x How reproducible: NA Steps to Reproduce: 1. Added the following line in /etc/sssd/sssd.conf to test for a login failure: command = valgrind -v --leak-check=full --trace-children=yes --show-reachable=yes --log-file=/var/log/sssd/valgrind_LDAP_%p.log /usr/libexec/sssd/sssd_be --domain LDAP --debug-to-files 2. 3. Actual results: Expected results: Additional info: