Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random
Bug #1708635 reported by
Alan Griffiths
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
util-linux (Ubuntu) |
Fix Released
|
Undecided
|
Chris Halse Rogers | ||
Bug Description
This has shown up in lp:mir CI on Artful amd64 (and no other architecture or series we're using)
For example:
Marking the memory with VALGRIND_
no longer affects: | valgrind (Ubuntu) |
Changed in util-linux (Ubuntu): | |
assignee: | nobody → Chris Halse Rogers (raof) |
Changed in util-linux (Ubuntu): | |
status: | New → Fix Committed |
To post a comment you must log in.
Looking at the util-linux source it seems that this could arise if:
1. opening /dev/urandom succeeds; and,
2. a subsequent read() fails