[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

2017-08-22 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.30.1-0ubuntu3 --- util-linux (2.30.1-0ubuntu3) artful; urgency=medium * Cherrypick upstream patches to support getrandom() fallbacks on older kernels. LP: #1708635 -- Dimitri John Ledkov Mon, 14 Aug 2017

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

2017-08-14 Thread Dimitri John Ledkov
** Changed in: util-linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1708635 Title: Valgrind reports " Uninitialised

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

2017-08-07 Thread Chris Halse Rogers
Already have done: https://github.com/karelzak/util-linux/pull/492 ☺ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1708635 Title: Valgrind reports " Uninitialised

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

2017-08-07 Thread Dimitri John Ledkov
Hi, Please provide minimal example of how to reproduce this. Ideally without the CI - as I see it tries to setup ccache / clang etc. And I'm not sure if all of that is relevant. You mention an older kernel, what kernel is that? I would have thought a reasonable kernel to test on, is latest

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

2017-08-06 Thread Chris Halse Rogers
** Changed in: util-linux (Ubuntu) Assignee: (unassigned) => Chris Halse Rogers (raof) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1708635 Title: Valgrind

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

2017-08-04 Thread Alan Griffiths
Not sure how to test this, but... index b93b9ba47..cfa82d13c 100644 --- a/lib/randutils.c +++ b/lib/randutils.c @@ -81,8 +81,10 @@ void random_get_bytes(void *buf, size_t nbytes) while (n > 0) { ssize_t x = read(fd, cp, n); if (x <=

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

2017-08-04 Thread Alan Griffiths
PS I suspect this only manifests in CI because the builders have an older kernel than development machines. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1708635 Title:

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

2017-08-04 Thread Alan Griffiths
Looking at the util-linux source it seems that this could arise if: 1. opening /dev/urandom succeeds; and, 2. a subsequent read() fails -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu.

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

2017-08-04 Thread Alan Griffiths
** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: valgrind (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu.