This bug was fixed in the package libqb - 1.0.3-1
---------------
libqb (1.0.3-1) unstable; urgency=medium
[ Christoph Berg ]
* [3e6a1ea] Remove Richard and myself from Uploaders
[ Ferenc Wágner ]
* [2dbb472] Update old style gbp.conf section names
* [c566381] New upstream release (1.0.3) (Closes: #871153, #877562)
* [2fa9704] Remove upstreamed/obsoleted patches, refresh the Hurd support
patch
* [13e68c7] Update symbols file.
Remove some internal symbols (see c011b12) and add a new one.
* [dc0438b] New patch: hurd: definition of PATH_MAX must be included
separately
* [737a79d] Update Standards-Version to 4.1.3 (no changes required)
* [1fc3d87] Switch to Debhelper compat level 11
* [930dba8] Combat test failures with a world-writeable socket directory.
On Linux systems libqb uses abstract sockets by default, which lack
access control. However, they aren't available on other platforms.
The other option is using file system sockets, by default under
/var/run. This directory is only writable by root, though, which
makes it inapproriate for unprivileged applications. So use /tmp
instead.
See also: https://github.com/ClusterLabs/libqb/issues/294
* [b7d5dea] New patch: tests: always run the SHM suite, just expect failures
* [419537a] New patch: hurd: the socket tests are expected to fail
(Closes: #803777)
* [ae9b078] Switch gbp dch to verbose changelog entries
* [75fc9d2] Stop repeating the common description
* [6e9aa99] Migrate to salsa.debian.org/ha-team
* [2093569] Whitespace cleanup in debian/changelog
* [5ad582f] Ship example code in the doc package
* [c6d7de2] Use secure URI in the Homepage field
* [0d73506] Modernize watch file, add signature checking
* [343b790] qb-blackbox makes libqb-dev not co-installable
* [fe6e555] Lintian does not emit embedded-javascript-library for Doxygen
anymore
* [42afbde] New patch: Fix spelling: plaform -> platform
-- Ferenc Wágner <wf...@debian.org> Wed, 14 Mar 2018 12:42:20 +0100
** Changed in: libqb (Ubuntu)
Status: Triaged => Fix Released
** Bug watch added: github.com/ClusterLabs/libqb/issues #294
https://github.com/ClusterLabs/libqb/issues/294
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1239109
Title:
aarch64 clock_gettime with CLOCK_REALTIME_COARSE or
CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV
Status in libqb package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
The aarch64 vDSO __kernel_clock_gettime implementation crashes when
clock_gettime is called with CLOCK_MONOTONIC_COARSE or
CLOCK_REALTIME_COARSE, with a SIGSEGV or SIGBUS respectively.
In the implementation
(http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/kernel/vdso/gettimeofday.S#n89)
a value other than CLOCK_REALTIME or CLOCK_MONOTONIC branches past the
usual "mov x2, x30" which preserves lr for return later. Anything
other than CLOCK_REALTIME_COARSE and CLOCK_MONOTONIC_COARSE then
branches directly to the svc call, which correctly returns to the
caller. But CLOCK_REALTIME_COARSE and CLOCK_MONOTONIC_COARSE execute
the special coarse path then fall through to the normal
CLOCK_REALTIME/CLOCK_MONOTONIC path, which does a 'ret x2' at the end,
despite not having saved x30 to x2 in the _COARSE case. So it ends up
setting pc to clk_id, which is either 4 or 5, giving a translation or
alignment fault.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1239109/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
