Created attachment 495060 [details]
Code to reproduce the problem

Description of problem:
Valgrind points out a possible memory leak while using crypt_r.
I reduced it to a tiny program which shows the problem in my system.


Version-Release number of selected component (if applicable):
$ uname -a
Linux MiguelDiaz.a2system 2.6.35.11-83.fc14.i686.PAE #1 SMP Mon Feb 7 06:57:55 UTC 2011 i686 i686 i386 GNU/Linux

$ yum info glibc
Loaded plugins: langpacks, presto, refresh-packagekit
Adding en_US to language list
Installed Packages
Name        : glibc
Arch        : i686
Version     : 2.13
Release     : 1


How reproducible:

--- Code to reproduce ---

#define _GNU_SOURCE

#include <stdio.h>
#include <string.h>
#include <crypt.h>

int main() {

	char *ptr;
	char res[50] = {0};
	char salt[] = "$1$protocHT";

	struct crypt_data data;
	data.initialized = 0;

	int i;
	for ( i = 0 ; i < 100 ; ++i ) {
		ptr = crypt_r("string_to_process", salt, &data);
		strcpy(res, ptr);
	}

	return 0;
	
}


--- Code to reproduce end ---

Steps to Reproduce:
1. Compile previous source code: $ gcc crypt.c -o crypt -lcrypt
2. Test under valgrind: valgrind --leak-check=full ./crypt
3. See the definitely lost column
  
Actual results:

==9926== 1,700 bytes in 100 blocks are definitely lost in loss record 1 of 1
==9926==    at 0x400677E: malloc (vg_replace_malloc.c:195)
==9926==    by 0x6CF00E: _dl_map_object (in /lib/ld-2.13.so)
==9926==    by 0x6D94F4: dl_open_worker (in /lib/ld-2.13.so)
==9926==    by 0x6D5785: _dl_catch_error (in /lib/ld-2.13.so)
==9926==    by 0x6D9BC5: _dl_open (in /lib/ld-2.13.so)
==9926==    by 0x891BCA: dlopen_doit (in /lib/libdl-2.13.so)
==9926==    by 0x6D5785: _dl_catch_error (in /lib/ld-2.13.so)
==9926==    by 0x89235B: _dlerror_run (in /lib/libdl-2.13.so)
==9926==    by 0x891C80: dlopen@@GLIBC_2.1 (in /lib/libdl-2.13.so)
==9926==    by 0x58EA7AD: ??? (in /lib/libfreebl3.so)
==9926==    by 0x58EADF1: NSSLOW_Init (in /lib/libfreebl3.so)
==9926==    by 0x571ACDC: __md5_crypt_r (in /lib/libcrypt-2.13.so)
==9926== 
==9926== LEAK SUMMARY:
==9926==    definitely lost: 1,700 bytes in 100 blocks
==9926==    indirectly lost: 0 bytes in 0 blocks
==9926==      possibly lost: 0 bytes in 0 blocks
==9926==    still reachable: 0 bytes in 0 blocks
==9926==         suppressed: 0 bytes in 0 blocks


Expected results:

==9926== All heap blocks were freed -- no leaks are possible

Additional info:
I want to know whether I'm misusing crypt_r or if there is an actual leak.