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:

The two memory leaks were fixed in snmplib on upstream. Our customer worked for that on the upstream. They have this memory leak issue actually on RHEL7 machine, and they would like us to backport the patches.

 [1] https://sourceforge.net/p/net-snmp/code/ci/c6facf2f080c9e1ea803e4884dc92889ec83d990/

 [2] https://sourceforge.net/p/net-snmp/code/ci/67726f2a74007b5b4117fe49ca1e02c86110b624/

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7.6

How reproducible:
Always with reproducer for second memory leak.
Customer can reproduce both memory leak.

Steps to Reproduce:
I will write it in another private comment.

Actual results:
memory leak happens.

Expected results:
memory leak doesn't happen.

Additional info:

The following is the related discussion on upstream.

First memory leak:

https://sourceforge.net/p/net-snmp/mailman/message/36436934/
https://sourceforge.net/p/net-snmp/mailman/message/36437024/

Second memory leak:

https://sourceforge.net/p/net-snmp/mailman/message/36437618/
https://sourceforge.net/p/net-snmp/mailman/message/36437956/

@dkutalek may I ask you for qa_ack?

Commit: http://pkgs.devel.redhat.com/cgit/rpms/net-snmp/commit/?id=0dded9a69e4bf0250013c8d4dd55de4b56c0c70f

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, 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-2019:2239