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.
Verified in nfs-utils-1.3.0-0.66.el7_8
~~~~~~~~
https://beaker.engineering.redhat.com/recipes/8432907#task111755402
-------------------------------------------------------------------
==12732== LEAK SUMMARY:
==12732== definitely lost: 0 bytes in 0 blocks
==12732== indirectly lost: 0 bytes in 0 blocks
==12732== possibly lost: 0 bytes in 0 blocks
==12732== still reachable: 92,362 bytes in 52 blocks
==12732== suppressed: 0 bytes in 0 blocks
==12732==
Compared with previous nfs-utils-1.3.0-0.66.el7
~~~~~~~
https://beaker.engineering.redhat.com/recipes/8172592#task109407324
-------------------------------------------------------------------
[22:19:49 root@ ~~]# grep '^==12512' /tmp/valgrind.out.32403 | awk '/LEAK SUMMARY/,/^==[[:digit:]]+== $/'
==12512== LEAK SUMMARY:
==12512== definitely lost: 812 bytes in 21 blocks
==12512== indirectly lost: 0 bytes in 0 blocks
==12512== possibly lost: 0 bytes in 0 blocks
==12512== still reachable: 93,358 bytes in 56 blocks
==12512== suppressed: 0 bytes in 0 blocks
==12512==
...
==12512== 56 bytes in 7 blocks are definitely lost in loss record 29 of 44
==12512== at 0x4C29F73: malloc (vg_replace_malloc.c:309)
==12512== by 0x5EBFAF9: strdup (in /usr/lib64/libc-2.17.so)
==12512== by 0x530DDE7: krb5_appdefault_string (in /usr/lib64/libkrb5.so.3.3)
==12512== by 0x111161: find_keytab_entry (krb5_util.c:796)
==12512== by 0x11209C: gssd_refresh_krb5_machine_credential (krb5_util.c:1277)
==12512== by 0x10F4BF: krb5_use_machine_creds (gssd_proc.c:546)
==12512== by 0x10F6EC: process_krb5_upcall (gssd_proc.c:655)
==12512== by 0x10FF38: handle_gssd_upcall (gssd_proc.c:814)
==12512== by 0x5C1EEA4: start_thread (in /usr/lib64/libpthread-2.17.so)
==12512== by 0x5F318DC: clone (in /usr/lib64/libc-2.17.so)
==12512==
==12512== 756 bytes in 14 blocks are definitely lost in loss record 38 of 44
==12512== at 0x4C29F73: malloc (vg_replace_malloc.c:309)
==12512== by 0x5EBFAF9: strdup (in /usr/lib64/libc-2.17.so)
==12512== by 0x110EC4: gssd_k5_err_msg (krb5_util.c:1324)
==12512== by 0x111610: find_keytab_entry (krb5_util.c:906)
==12512== by 0x11209C: gssd_refresh_krb5_machine_credential (krb5_util.c:1277)
==12512== by 0x10F4BF: krb5_use_machine_creds (gssd_proc.c:546)
==12512== by 0x10F6EC: process_krb5_upcall (gssd_proc.c:655)
==12512== by 0x10FF38: handle_gssd_upcall (gssd_proc.c:814)
==12512== by 0x5C1EEA4: start_thread (in /usr/lib64/libpthread-2.17.so)
==12512== by 0x5F318DC: clone (in /usr/lib64/libc-2.17.so)
==12512==
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 (nfs-utils 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:3351