#2138 Valgrind sssd "Syscall param socketcall.sendto(msg) points to uninitialised byte(s)"
Closed: Fixed None Opened 5 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1023409

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:

When debugging a memory leak issue in the case 00967661 we found an unrelated
bug with Valgrind. I'm opening this BZ just in case it's relevant.


Version-Release number of selected component (if applicable):

sssd-1.9.2-82.4.el6_4.x86_64
sssd-client-1.9.2-82.4.el6_4.x86_64


How reproducible:

Uncertain.


Steps to Reproduce:
1.
2.
3.

Actual results:

From case description (2013-10-18 09:32:16Z):

[root@sputnik log]# ps -e -o 'vsz pid ruser cpu time args' |sort -nr|grep sssd
6038424 27356 root      - 01:59:27 /usr/libexec/sssd/sssd_nss --debug-to-files
227720 27355 root       - 00:01:36 /usr/libexec/sssd/sssd_be --domain default
--debug-to-files
198108 27354 root       - 00:02:32 /usr/sbin/sssd -f -D
189720 27357 root       - 00:01:06 /usr/libexec/sssd/sssd_pam --debug-to-files
103236 25114 root       - 00:00:00 grep sssd
[root@sputnik log]# /etc/init.d/sssd restart
Stopping sssd:                                             [  OK  ]
Starting sssd:                                             [  OK  ]
[root@sputnik log]# ps -e -o 'vsz pid ruser cpu time args' |sort -nr|grep sssd
217444 25148 root       - 00:00:00 /usr/libexec/sssd/sssd_be --domain default
--debug-to-files
199404 25149 root       - 00:00:00 /usr/libexec/sssd/sssd_nss --debug-to-files
198108 25147 root       - 00:00:00 /usr/sbin/sssd -f -D
189588 25150 root       - 00:00:00 /usr/libexec/sssd/sssd_pam --debug-to-files
103236 25154 root       - 00:00:00 grep sssd


And, the Valgrind test (23/10/2013 12:25):

[root@sputnik tmp]# ps -e -o 'vsz pid ruser cpu time args' |sort -nr|grep sssd
675532   350 root       - 00:41:04 valgrind --leak-check=full
--log-file=/tmp/valgrind.%p.log /usr/libexec/sssd/sssd_nss
217656   349 root       - 00:00:02 /usr/libexec/sssd/sssd_be --domain default
--debug-to-files
198200   348 root       - 00:00:03 /usr/sbin/sssd -f -D
189616   351 root       - 00:00:01 /usr/libexec/sssd/sssd_pam --debug-to-files
103236 27958 root       - 00:00:00 grep sssd


And the content of the file :

[root@sputnik tmp]# cat /tmp/valgrind.350.log
==350== Memcheck, a memory error detector
==350== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==350== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==350== Command: /usr/libexec/sssd/sssd_nss
==350== Parent PID: 348
==350==
==350== Syscall param socketcall.sendto(msg) points to uninitialised byte(s)
==350==    at 0x7A6BA82: send (send.c:28)
==350==    by 0x43352F: sss_packet_send (responder_packet.c:229)
==350==    by 0x42BB6A: client_fd_handler (responder_common.c:245)
==350==    by 0x4E363FE: std_event_loop_once (tevent_standard.c:328)
==350==    by 0x4E328EF: _tevent_loop_once (tevent.c:507)
==350==    by 0x4E3295A: tevent_common_loop_wait (tevent.c:608)
==350==    by 0x45A1B2: server_loop (server.c:601)
==350==    by 0x40909F: main (nsssrv.c:564)
==350==  Address 0x13617b30 is 112 bytes inside a block of size 592 alloc'd
==350==    at 0x4C279EE: malloc (vg_replace_malloc.c:270)
==350==    by 0x503FCA0: talloc_named_const (talloc.c:560)
==350==    by 0x4337D2: sss_packet_new (responder_packet.c:70)
==350==    by 0x409FC7: nss_cmd_initgr_send_reply (nsssrv_cmd.c:3562)
==350==    by 0x413047: nss_cmd_initgroups_dp_callback (nsssrv_cmd.c:3726)
==350==    by 0x40B7D3: nsssrv_dp_send_acct_req_done (nsssrv_cmd.c:643)
==350==    by 0x4328AD: sss_dp_internal_get_done (responder_dp.c:763)
==350==    by 0x5480619: complete_pending_call_and_unlock
(dbus-connection.c:2234)
==350==    by 0x548286E: dbus_connection_dispatch (dbus-connection.c:4397)
==350==    by 0x45885D: sbus_dispatch (sssd_dbus_connection.c:104)
==350==    by 0x4E36BD8: tevent_common_loop_timer_delay (tevent_timed.c:254)
==350==    by 0x4E362AA: std_event_loop_once (tevent_standard.c:560)
==350==


Expected results:

Uncertain


Additional info:

For feedback please refer to Jakub Hrozek (jhrozek@redhat.com) who is
collaborating with the above case.

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.11.3
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

owner: somebody => lslebodn
status: new => assigned

Fields changed

patch: 0 => 1

resolution: => fixed
status: assigned => closed

Fields changed

changelog: => N/A, not visible to end user

Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.11.3

2 years ago

Login to comment on this ticket.

Metadata