Bug 416464 - [Patch] Fix false reports for uninitialized memory for PR_CAPBSET_READ/DROP
Summary: [Patch] Fix false reports for uninitialized memory for PR_CAPBSET_READ/DROP
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 3.15 SVN
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-19 16:09 UTC by Stefan Brüns
Modified: 2020-01-22 09:47 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Update prctl constants (1.91 KB, patch)
2020-01-19 16:09 UTC, Stefan Brüns 		Details
Handle PR_CAPBSET_READ/DROP (1.08 KB, patch)
2020-01-19 16:09 UTC, Stefan Brüns 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Brüns 2020-01-19 16:09:22 UTC 
Created attachment 125243 [details]
Update prctl constants

SUMMARY

Valgrind does not recognize the PR_CAPBSET_* syscalls and thus defaults to
check for 5 parameters instead of two (including syscall number).

Current versions of libcap make use of PR_CAPBSET_READ calls and valgrind
reports an error.
Comment 1 Stefan Brüns 2020-01-19 16:09:58 UTC 
Created attachment 125244 [details]
Handle PR_CAPBSET_READ/DROP
Comment 2 Julian Seward 2020-01-22 09:45:27 UTC 
(In reply to Stefan Brüns from comment #1)
> Created attachment 125244 [details]
> Handle PR_CAPBSET_READ/DROP

This patch misses a "break;" statement.
Comment 3 Julian Seward 2020-01-22 09:47:04 UTC 
Committed (+ an extra break), 685247b67a6104b71131de6ae6b2e455786a83ad.
Thanks for the patch.