summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2014-09-04Make dbus-1 dependency provided by dbussubmit/tizen/20140918.170127accepted/tizen/ivi/20140927.211752accepted/tizen/common/20140919.144001Jacek Bukarewicz2-1/+1
dbus-1 was originally provided by dbus package. Commit 8eeae5fd70 fixed circular dependency between dbus and systemd. It also moved dbus-1 provision from dbus to dbus-devel probably by mistake. Certain packages like gumd or polkit have explicit dependency on dbus-1 which makes them install dbus-devel unnecessarily. Change-Id: I77a6561eff6f8c6ce84d849df936dda2c290a4d2 Signed-off-by: Jacek Bukarewicz <j.bukarewicz@samsung.com>
2014-02-06dbus-x11 should not try to build into a pure wayland platform.submit/tizen_ivi_release/20140312.071218submit/tizen/20140312.070743submit/tizen/20140307.080703submit/tizen/20140212.081706accepted/tizen/mobile/20140310.024737accepted/tizen/mobile/20140225.043831accepted/tizen/ivi/release/20140312.121253accepted/tizen/ivi/panda/20140312.101101accepted/tizen/ivi/20140212.232051accepted/tizen/generic/20140312.095952accepted/tizen/generic/20140212.083543Ronan Le Martret1-0/+6
This package is designed for an X server platform. In a system released, based exclusively on Wayland platform, it should be in a excluded status. Tizen devel | Tizen release _____________|______________ succeeded | succeeded excluded | excluded broken | failed | unresolvable | blocked | locked | note: - The disabled status is only allowed for OBS administration. Change-Id: I1495b66a2e32b580223229ead6bc66426ff680a6 Signed-off-by: Ronan Le Martret <ronan@fridu.net>
2013-11-25libdbus:build-require pkg-configsubmit/tizen/20131213.193902submit/tizen/20131213.192627submit/tizen/20131213.190823submit/tizen/20131213.185738accepted/tizen/ivi/20131213.192509accepted/tizen/ivi/20131213.190535Adrian Negreanu1-0/+1
otherwise, configure fails to find libsmack, which happens to be the first lib searched with pkg-config checking for _NSGetEnviron... no checking for LIBSMACK... configure: error: libsmack is required to enable smack support error: Bad exit status from /var/tmp/rpm-tmp.VUiY9N Change-Id: Ibf01a52ae6274503e2490f835fbd686e985807e8 Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>
2013-10-07packaging: enable Smack supportsubmit/tizen_ivi_stable/20131213.015832submit/tizen_ivi_stable/20131213.015224submit/tizen/20131220.014054submit/tizen/20131219.030924submit/tizen/20131213.205734submit/tizen/20131213.020319submit/tizen/20131213.020141submit/tizen/20131010.194211accepted/tizen/mobile/20131223.191827accepted/tizen/mobile/20131216.220150accepted/tizen/ivi/20131220.020933accepted/tizen/ivi/20131219.030826accepted/tizen/ivi/20131213.205528accepted/tizen/generic/20140106.140246accepted/tizen/20131213.020036accepted/tizen/20131010.203702accepted/tizen/20131010.203629Patrick McCarty4-3/+14
Change-Id: Ib400feec8193bb5c98347b778e0aa92a30d954c3 Signed-off-by: Patrick McCarty <patrick.mccarty@linux.intel.com>
2013-09-10Install dbus directoriessubmit/tizen_ivi_release/20131211.020401submit/tizen_ivi_genivi/20140131.024328submit/tizen/20130911.195727submit/tizen/20130911.094146submit/tizen/20130910.230842ivi_oct_m2accepted/tizen_ivi_release/20131211.022842accepted/tizen/ivi/genivi/20140131.024645accepted/tizen/20130912.015042accepted/tizen/20130911.195343accepted/tizen/20130911.195321accepted/tizen/20130911.195037accepted/tizen/20130911.195025accepted/tizen/20130911.152501Chengwei Yang1-0/+7
At previous, these directories owned by libdbus. However, the previous commit 8eeae5f split libdbus into a separate .spec and doesn't install these directoris. These directoris are critical to dbus, for example, without /etc/dbus-1/{system.d,session.d}, the dbus-daemon system bus and session bus can not launch. Change-Id: Ia98bd56171492c90e4a078b39adf08cc802cb955
2013-08-06fix systemd->dbus->systemd circular dependencysubmit/tizen/20130902.144059Adrian Negreanu2-58/+124
extract libdbus and dbus-devel as separate packages Change-Id: Ia097a2b3fee2911ee89000dd2d5762a112bf17f6 Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>
2013-07-22updating changelogsubmit/tizen/20130722.203302submit/tizen/20130722.125706accepted/tizen/20130722.202946Michael Leibowitz1-0/+5
2013-07-10Enforce smack policy from conf fileBrian McGillion5-19/+278
2013-07-10Enable checking of smack context from DBus interfaceBrian McGillion7-3/+199
2013-06-28resetting manifest requested domain to floorsubmit/tizen/20130710.130132accepted/tizen/20130710.220936Alexandru Cornea2-0/+8
2013-06-20Update to dbus 1.6.12submit/tizen/20130620.124407Anas Nashif4-6/+8
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2013-06-19update changelogsubmit/tizen/20130620.084139Simon McVittie1-0/+4
- TZPC-3044, CVE-2013-2168: fix local denial of service (backport from 1.6.12) - TZPC-1971: make libdbus thread-safe by default (backport from 1.7.4/1.7.6)
2013-06-19Add a statically-initialized implementation of _dbus_lock() on glibc systemsSimon McVittie3-0/+67
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=54972 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Alban Crequy <alban.crequy@collabora.co.uk> Reviewed-by: Anas Nashif <anas.nashif@intel.com> Bug-Tizen: TZPC-1971 Applied-upstream: 1.7.6, commit:83aaa9f359e90d3b8cae5d17f6d9ba4600cff68b Change-Id: Iee8ec5e2138ad8398efbe1cd16b46e61cee08670
2013-06-19Always initialize threading before allocating a dynamic mutexSimon McVittie1-244/+56
Dynamic allocation of mutexes can fail anyway, so this is easy. Justification for not keeping the dummy mutex code-paths, even as an opt-in thing for processes known to be high-performance and single-threaded: real mutexes only cut the throughput of test/dbus-daemon.c by a couple of percent on my laptop (from around 6700 to around 6600 messages per second), and libdbus crashes caused by not calling dbus_threads_init_default() are sufficiently widespread that they're wasting a lot of everyone's time. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=54972 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Alban Crequy <alban.crequy@collabora.co.uk> Reviewed-by: Anas Nashif <anas.nashif@intel.com> Bug-Tizen: TZPC-1971 Applied-upstream: 1.7.6, commit:08391b14616c248458e838691d068aa48dc70d18 Change-Id: I62e4fc541f6868ef44dc0654337b895e5392c16e
2013-06-19Make taking a global lock automatically initialize locking if neededSimon McVittie14-71/+213
This lets them be thread-safe by default, at the cost that they can now fail. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=54972 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Alban Crequy <alban.crequy@collabora.co.uk> Reviewed-by: Anas Nashif <anas.nashif@intel.com> Applied-upstream: 1.7.6, commit:2b3272c75ae48c93911bd6f656965cf77d6de3e8 Bug-Tizen: TZPC-1971 Change-Id: I7e547e5776d37051ec8b6eccc2c8bd34b8d1996b
2013-06-19Replace individual global-lock variables with an array of DBusRMutex *Simon McVittie15-184/+126
This means we can use a much simpler code structure in data-slot allocators: instead of giving them a DBusRMutex ** at first-allocation, we can just give them an index into the array, which can be done statically. It doesn't make us any more thread-safe-by-default - the mutexes will only actually be used if threads were already initialized - but it's substantially better than nothing. These locks really do have to be recursive: for instance, internal_bus_get() calls dbus_bus_register() under the bus lock, and dbus_bus_register() can call _dbus_connection_close_possibly_shared(), which takes the bus lock. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=54972 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Alban Crequy <alban.crequy@collabora.co.uk> Reviewed-by: Ralf Habacker <ralf.habacker@freenet.de> Reviewed-by: Anas Nashif <anas.nashif@intel.com> Applied-upstream: 1.7.6, commit:c80c20af46c5f43dcbe672f2c6d8aec0e7f2bbd6 Bug-Tizen: TZPC-1971 Change-Id: I22a31a9278b5f9c88557c54723f86827a91de818
2013-06-19Turn a runtime assertion into a compile-time assertionSimon McVittie1-2/+1
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=54972 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Alban Crequy <alban.crequy@collabora.co.uk> Reviewed-by: Ralf Habacker <ralf.habacker@freenet.de> Applied-upstream: 1.7.4, commit:24a9b93021908b6f2b20eaacc1b36fa8fb24edb4 Bug-Tizen: TZPC-1971 Reviewed-by: Anas Nashif <anas.nashif@intel.com> Change-Id: I2784b0aa9046fba5a83065d32305c127a2a2dc78
2013-06-19Remove unused global mutexes for win_fds, sid_atom_cacheSimon McVittie3-10/+4
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=54972 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Alban Crequy <alban.crequy@collabora.co.uk> Reviewed-by: Ralf Habacker <ralf.habacker@freenet.de> Applied-upstream: 1.7.4, commit:d35f64339e401a7a47c1b088ef26e3dcb202cb9d Bug-Tizen: TZPC-1971 Reviewed-by: Anas Nashif <anas.nashif@intel.com> Change-Id: I9619eaf477eaf1763133772b95e3845dd7c2b62e
2013-06-19dbus_threads_init_default, dbus_threads_init: be safe to call at any timeSimon McVittie9-7/+139
On Unix, we use a pthreads mutex, which can be allocated and initialized in global memory. On Windows, we use a CRITICAL_SECTION, together with a call to InitializeCriticalSection() from the constructor of a global static C++ object (thanks to Ralf Habacker for suggesting this approach). Bug: https://bugs.freedesktop.org/show_bug.cgi?id=54972 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Alban Crequy <alban.crequy@collabora.co.uk> Reviewed-by: Ralf Habacker <ralf.habacker@freenet.de> Applied-upstream: 1.7.4, commit:17a23d08b51cf21a2110047649a86445e99e2b3f Bug-Tizen: TZPC-1971 Reviewed-by: Anas Nashif <anas.nashif@intel.com> Change-Id: Id6aa81b7d553965c4c6f511e2410673c2f222a66
2013-06-19dbus_threads_init: call _dbus_threads_init_platform_specific()Simon McVittie3-5/+7
This reverses the relationship between these two functions. Previously, dbus_threads_init() wouldn't allocate dbus_cond_event_tls on Windows, call check_monotonic_clock on Unix, or call _dbus_check_setuid on Unix. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=54972 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Alban Crequy <alban.crequy@collabora.co.uk> Reviewed-by: Ralf Habacker <ralf.habacker@freenet.de> Applied-upstream: 1.7.4, commit:eabf6c42a1b779f57f2c08d35772035788657579 Bug-Tizen: TZPC-1971 Change-Id: Ice70cf1f3e2202b72016daf619c89206b96aac47
2013-06-19DBusAtomic: on Unix, use pthreads mutexes for fallbackSimon McVittie4-17/+20
On pthreads platforms, POSIX guarantees that we can "allocate" mutexes as library-global variables, without involving malloc. This means we don't need to error-check their allocation - if the dynamic linker succeeds, then we have enough memory for all our globals - which is an important step towards being thread-safe by default. In particular, making atomic operations never rely on DBusMutex means that we are free to implement parts of DBusMutex in terms of DBusAtomic, if it would help. We do not currently support any non-Windows platform that does not have pthreads. This is unlikely to change. On Windows, we already used real atomic operations; we can just delete the unused global variable. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=54972 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Alban Crequy <alban.crequy@collabora.co.uk> Reviewed-by: Ralf Habacker <ralf.habacker@freenet.de> Applied-upstream: 1.7.4, commit:c36f21a2e91730e9ae52e8945305aa3072f0e508 Bug-Tizen: TZPC-1971 Change-Id: I91d99a86f25d49d63d79eebfe85767bb8cc66170
2013-06-19Add _DBUS_GNUC_WARN_UNUSED_RESULT, similar to GLib'sSimon McVittie1-1/+9
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=54972 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Ralf Habacker <ralf.habacker@freenet.de> Reviewed-by: Alban Crequy <alban.crequy@collabora.co.uk> Applied-upstream: 1.7.4, commit:7ac9b68220a2f48bc2942aaa909d6ba1f4605f73 Bug-Tizen: TZPC-1971 Change-Id: I9944ae3a1e9901728bbc3bedbcc6474022db586f
2013-06-19packaging: ensure ownership for /var/lib/dbusPatrick McCarty2-4/+7
For x86_64 builds, %{_localstatedir}%{_libdir}/dbus expands to /var/usr/lib64/dbus, which is incorrect. This commit fixes the path in the spec to make sure the intended directory, /var/lib/dbus, is created and owned by this package. Change-Id: I60947c4e2c221ad2f83d01bd87dc76fc8f5e4433
2013-06-19Update to 1.6.10Anas Nashif1-0/+3
2013-06-19update to 1.6.10Anas Nashif2-3/+3
2013-06-19Adapt for rebase onto upstream dbus-1.6.8 git tagSimon McVittie2-0/+5
When building from git we need a BuildRequires on xmlto, since we can no longer rely on the pre-generated HTML documentation from the tarball. That pulls in libxslt-tools, which means dbus.devhelp is generated, so the build fails because we weren't accounting for that; so explicitly require libxslt-tools too (dbus uses it both via xmlto, and directly), and package dbus.devhelp. Change-Id: I7505fc6fd1e7c4fc23a53f349a4fdd18d88237ec
2013-06-19Cleanup lib name in specAnas Nashif1-0/+3
2013-06-19use libname directlyAnas Nashif1-7/+6
2013-06-19Fixed package groupsAnas Nashif4-7/+9
2013-06-19No OOMScoreAdjust for user sessionAnas Nashif2-2/+3
2013-06-19add user session unitsAnas Nashif1-1/+3
2013-06-19add user session unitsAnas Nashif4-3/+35
2013-06-19initial changelogSimon McVittie1-0/+5
2013-06-19regenerate packaging/dbus-x11.spec with ( cd packaging && sh pre_checkin.sh )Simon McVittie1-5/+1
Otherwise, local builds with 'gbs build' try to apply the nonexistent patch 0001-fix-sba-for-dbus-activation.patch, and fail.
2013-06-19fixed splittingAnas Nashif1-1/+1
2013-06-19fixed splittingAnas Nashif1-1/+1
2013-06-19fixed splittingAnas Nashif1-1/+1
2013-06-19Fixed package splittingAnas Nashif4-36/+18
split dbus-x11 correctly
2013-06-19spec cleanup and removed patchesAnas Nashif1-27/+1
2013-06-19Set correct address when using --address=systemd:Simon Peeters3-13/+97
When dbus gets launched through systemd, we need to create an address string based on the sockets passed. The _dbus_append_addres_from_socket() function is responsible for extracting the address information from the file-descriptor and formatting it in a dbus friendly way. This fixes bus activation when running dbus under a systemd session. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=50962 Signed-off-by: Simon Peeters <peeters.simon@gmail.com> Applied-upstream: 1.7.0, commit:d728fdc655f17031da3bb129ab2fd17dadf0fe3a
2013-06-19add packagingAnas Nashif7-0/+564
2013-06-12Prepare embargoed release for tomorrowdbus-1.6.12Simon McVittie2-3/+7
2013-06-12Add a test-case for CVE-2013-2168Simon McVittie2-0/+94
Reviewed-by: Thiago Macieira <thiago@kde.org> [build system adjusted to compile it even if we don't have GLib -smcv]
2013-06-12CVE-2013-2168: _dbus_printf_string_upper_bound: copy the va_list for each useSimon McVittie2-5/+20
Using a va_list more than once is non-portable: it happens to work under the ABI of (for instance) x86 Linux, but not x86-64 Linux. This led to _dbus_printf_string_upper_bound() crashing if it should have returned exactly 1024 bytes. Many system services can be induced to process a caller-controlled string in ways that end up using _dbus_printf_string_upper_bound(), so this is a denial of service. Reviewed-by: Thiago Macieira <thiago@kde.org>
2013-06-12NEWS for 1.6.xSimon McVittie1-1/+10
2013-06-12Fix dbus-daemon crash due to invalid service fileChengwei Yang1-0/+6
dbus-daemon will crash due to invalid service file which key/value starts before section. In that situation, new_line() will try to access invalid address. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=60853 Signed-off-by: Chengwei Yang <chengwei.yang@intel.com> Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
2013-06-05Fix build error: unused-resultChengwei Yang1-2/+8
Signed-off-by: Chengwei Yang <chengwei.yang@intel.com> Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
2013-06-05When "activating" systemd, handle its special case betterChengwei Yang1-5/+14
When dbus-daemon receives a request to activate a systemd service before systemd has connected to it, it enqueues a fake request to "activate" systemd itself (as a way to get a BusPendingActivationEntry to track the process of waiting for systemd). When systemd later joins the bus, dbus-daemon sends the actual activation message; any future activation messages are sent directly to systemd. In the "pending" code path, the activation messages are currently dispatched as though they had been sent by the same process that sent the original activation request, which is wrong: the bus security policy probably doesn't allow that process to talk to systemd directly. They should be dispatched as though they had been sent by the dbus-daemon itself (connection == NULL), the same as in the non-pending code path. In the worst case, if the attempt to activate systemd timed out, the dbus-daemon would crash with a (fatal) warning, because in this special case, activation_message is a signal with no serial number, whereas the code to send an error reply is expecting a method call with a serial number. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=50199 Signed-off-by: Chengwei Yang <chengwei.yang@intel.com> Tested-by: Ma Yu <yu.ma@intel.com> Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
2013-04-24development versionSimon McVittie2-1/+6
2013-04-24Prepare release 1.6.10upstream/1.6.10dbus-1.6.10Simon McVittie2-3/+5
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-25 13:37:57 +0000