Red Hat Bugzilla – Bug 88537
CAN-2003-0211 xinetd leaks memory
Last modified: 2014-08-31 19:24:49 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
Description of problem:
xinetd leaks 144 bytes of memory for each rejected connection.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Setup chargen with access_times = 5:00-9:00 this is just to make sure the
connection is rejected. Then stop xinetd and run via valgrind:
valgrind --leak-check=yes --leak-resolution=med --num-callers=8 --logfile-fd=9
/usr/sbin/xinetd -d -pidfile /var/run/xinetd.pid -stayalive 9> out.txt
next, telnet localhost chargen
stop xinetd and open out.txt captured from valgrind.
Actual Results: ==18939== 144 bytes in 1 blocks are definitely lost in loss
record 36 of 45
==18939== at 0x40160DB8: malloc (vg_clientfuncs.c:103)
==18939== by 0x804FE22: (within /usr/sbin/xinetd)
==18939== by 0x805A496: (within /usr/sbin/xinetd)
==18939== by 0x8053611: (within /usr/sbin/xinetd)
==18939== by 0x805340D: (within /usr/sbin/xinetd)
==18939== by 0x40294A46: __libc_start_main (in /lib/libc-2.3.2.so)
==18939== by 0x804A310: (within /usr/sbin/xinetd)
Expected Results: No leaks.
The 144 byte loss is cumulative. Xinetd in cvs at xinetd.org has the memory
leaks fixed and will be releasing 2.3.11 rsn to address this.
Errata in progress
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.