New branch 'upstream-unstable' available with the following commits:
commit 0ff73b7666b8aee1a68302dd6a7664b68aa659af
Author: Bryce Harrington <br...@osg.samsung.com>
Date: Tue Feb 16 12:03:40 2016 -0800
configure.ac: bump to version 1.10.0 for the official release
commit bf34ac75d0d61609296de1300196c843f4246e7c
Author: Jonas Ådahl <jad...@gmail.com>
Date: Wed Feb 10 23:35:44 2016 +0800
connection: Don't add uninitialized memory as 4 byte alignment padding
When we are adding padding bytes making our wl_buffer buffer content 4
byte aligned, we are just moving the pointer. Since the buffer is
allocated using plain malloc(), this means our padding bytes are
effectively uninitialized data, which could be anything previously
allocated in the server process. As we'll be sharing this buffer
content with arbitrary clients, we are effectively sharing private
memory with every client, and even though a well behaving client will
discard any such memory, a malicious client may not.
Therefor, to avoid any potential missuse of the uninitialized padding
memory shared between the server and client, initialize the buffer
content to 0, making the padding bytes always 0.
Signed-off-by: Jonas Ådahl <jad...@gmail.com>
Reviewed-by: Derek Foreman <der...@osg.samsung.com>
Reviewed-by: Pekka Paalanen <pekka.paala...@collabora.co.uk>
Reviewed-by: Bryce Harrington <br...@osg.samsung.com>
commit 1906a90aab613501396fe4fb72c7fba9e13ee161
Author: Bryce Harrington <br...@osg.samsung.com>
Date: Tue Feb 9 13:26:21 2016 -0800
configure.ac: bump to version 1.9.93 for the RC1 release
commit d33514379d311bd9ddd4a2e1e97c8205a8111d3c
Author: Sergi Granell <xerpi.g...@gmail.com>
Date: Thu Feb 4 21:48:21 2016 +0100
cosmetic: add an space after if
commit 6301639146474795da10952db86ea3ef4849f568
Author: Sergi Granell <xerpi.g...@gmail.com>
Date: Thu Feb 4 21:35:07 2016 +0100
cosmetic: use tabs instead of spaces
commit 369b6466a71175289572c4ef8f70af65f620fb88
Author: Derek Foreman <der...@osg.samsung.com>
Date: Tue Feb 2 14:56:57 2016 -0600
scanner: Fix oddities in copyright printing
Some copyright strings could result in broken generated header files with
unmatched */
This change:
Runs the loop long enough so the copyright[i] == 0 test can actually
happen. (if there was no \n no copyright text was printed, */ still was)
Prints the opening /* even if there was whitespace at the start of
the very first line.
Only emits a */ if a /* was printed.
Signed-off-by: Derek Foreman <der...@osg.samsung.com>
Reviewed-by: Jon A. Cruz <j...@osg.samsung.com>
Reviewed-by: Bryce Harrington <br...@osg.samsung.com>
