Fixed valgrind error #253
Open
Fixed valgrind error #253
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixed the following valgrind report by initializing 'buffer' to 0 in 'svc_dg_reply': ==2615== Syscall param sendmsg(msg.msg_control) points to uninitialised byte(s) ==2615== at 0x6651C6D: ??? (in /usr/lib64/libpthread-2.17.so) ==2615== by 0x6A8A9E1: svc_dg_reply (svc_dg.c:465) ==2615== by 0x6A88748: svc_sendreply (svc.c:549) ==2615== by 0x44CDF2: nfs_rpc_execute (nfs_worker_thread.c:1344) ==2615== by 0x44D447: worker_run (nfs_worker_thread.c:1562) ==2615== by 0x50C4FF: fridgethr_start_routine (fridgethr.c:550) ==2615== by 0x664AE24: start_thread (in /usr/lib64/libpthread-2.17.so) ==2615== by 0x6FC434C: clone (in /usr/lib64/libc-2.17.so) ==2615== Address 0x1360ce08 is on thread 17's stack ==2615== in frame nfs-ganesha#1, created by svc_dg_reply (svc_dg.c:407) Signed-off-by: Prabhu Murugesan <[email protected]>
dang
approved these changes
Jul 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed the following valgrind report by initializing
'buffer' to 0 in 'svc_dg_reply':
==2615== Syscall param sendmsg(msg.msg_control) points to uninitialised byte(s)
==2615== at 0x6651C6D: ??? (in /usr/lib64/libpthread-2.17.so)
==2615== by 0x6A8A9E1: svc_dg_reply (svc_dg.c:465)
==2615== by 0x6A88748: svc_sendreply (svc.c:549)
==2615== by 0x44CDF2: nfs_rpc_execute (nfs_worker_thread.c:1344)
==2615== by 0x44D447: worker_run (nfs_worker_thread.c:1562)
==2615== by 0x50C4FF: fridgethr_start_routine (fridgethr.c:550)
==2615== by 0x664AE24: start_thread (in /usr/lib64/libpthread-2.17.so)
==2615== by 0x6FC434C: clone (in /usr/lib64/libc-2.17.so)
==2615== Address 0x1360ce08 is on thread 17's stack
==2615== in frame #1, created by svc_dg_reply (svc_dg.c:407)
Signed-off-by: Prabhu Murugesan [email protected]