MSan doesn't catch uninitialized reads in send() or sendmsg() |
||||
Issue descriptionTypically we intercept syscalls such as write() in MSan builds to ensure that uninitialized bytes aren't used for interesting system calls. We use send() and sendmsg() for IPC on most POSIX systems, but these don't appear to be intercepted. As such, uninitialized bytes may be sent freely via these calls without MSan complaining. This seems like something we should fix.
,
Jun 14 2016
,
Jun 17 2016
Should be fixed upstream in r272980. http://llvm.org/viewvc/llvm-project?rev=272980&view=rev
,
Jun 21 2016
,
Jun 28 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by thakis@chromium.org
, Jun 14 2016