summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2015-06-10networkd: bond improve loggingSusant Sahani
Replaces a lof of strerror() usage with log_netdev_error_errno()
2015-06-10logind,sd-event: drop spurious new-linesLennart Poettering
2015-06-10tree-wide: whenever we fork off a foreign child process reset signal ↵Lennart Poettering
mask/handlers Also, when the child is potentially long-running make sure to set a death signal. Also, ignore the result of the reset operations explicitly by casting them to (void).
2015-06-10signal-util: modernize and share more codeLennart Poettering
2015-06-09Merge pull request #126 from phomes/masterLennart Poettering
core: log oom during killing spree
2015-06-09core: log oom during killing spreeThomas Hindoe Paaboel Andersen
but don't do anything else. We still want to kill as much as possible. Coverity CID#996306
2015-06-09Merge pull request #122 from martinpitt/masterLennart Poettering
path-util: Fix path_is_mount_point for parent mount points in symlink mode
2015-06-09path-util: Fix path_is_mount_point for parent mount points in symlink modeMartin Pitt
When we have a structure like this: /bin -> /usr/bin /usr is a mount point Then path_is_mount_point("/bin", AT_SYMLINK_FOLLOW) needs to look at the pair /usr/bin and /usr, not at the pair / and /usr/bin, as the latter have different mount IDs. But we only want to consider the base name, not any parent. Thus we have to resolve the given path first to get the real parent when allowing symlinks. Bug: https://github.com/systemd/systemd/issues/61
2015-06-09Merge pull request #121 from martinpitt/masterLennart Poettering
build-sys: always dist *.policy.in files
2015-06-09build-sys: always dist *.policy.in filesMartin Pitt
Unconditionally dist org.freedesktop.{import1,machine1}.policy.in, like all the other *.policy.in files. This avoids missing policy files in the tarball. Spotted by "make distcheck" failure with --disable-importd.
2015-06-09Merge pull request #111 from phomes/cleanup_warning_suppressionLennart Poettering
build-sys: don't suppress irrelevant warnings
2015-06-09Merge pull request #120 from systemd/revert-115-masterKay Sievers
Revert "hwdb: actually search /run/udev/hwdb.d"
2015-06-09Revert "hwdb: actually search /run/udev/hwdb.d"Lennart Poettering
2015-06-09Merge pull request #118 from haraldh/set_consume2Lennart Poettering
util:bind_remount_recursive() fix "use after free" - 2
2015-06-09Merge pull request #77 from haraldh/cryptsetupLennart Poettering
cryptsetup: craft a unique ID with the source device
2015-06-09Merge pull request #116 from utezduyar/feat/async-api-for-method-callLennart Poettering
sd-bus: add async convenience method call API
2015-06-09Merge pull request #113 from mezcalero/address-familyLennart Poettering
networkd: actually always use AddressFamilyBoolean as the bit mask it is
2015-06-09util:bind_remount_recursive(): handle return 0 of set_consume()Harald Hoyer
set_consume() does not return -EEXIST, but 0, in case the key is already in the Set.
2015-06-09Revert "util:bind_remount_recursive() fix "use after free""Harald Hoyer
This reverts commit 46be6129d3e52556eb0f2ae4d07818f9f3f7af7a.
2015-06-09cryptsetup: craft a unique ID with the source deviceHarald Hoyer
If cryptsetup is called with a source device as argv[3], then craft the ID for the password agent with a unique device path. If possible "/dev/block/<maj>:<min>" is used, otherwise the original argv[3] is used. This enables password agents like petera [1] to provide a password according to the source device. The original ID did not carry enough information and was more targeted for a human readable string, which is specified in the "Message" field anyway. With this patch the ID of the ask.XXX ini file looks like this: ID=cryptsetup:/dev/block/<maj>:<min> [1] https://github.com/npmccallum/petera
2015-06-09sd-bus: add async convenience method call APIUmut Tezduyar Lindskog
2015-06-09Merge pull request #115 from whot/masterMartin Pitt
hwdb: actually search /run/udev/hwdb.d
2015-06-09Merge pull request #114 from crawford/xenMartin Pitt
rules: whitelist xvd* devices
2015-06-09hwdb: actually search /run/udev/hwdb.dPeter Hutterer
The documentation claims hwdb entries may be placed in the volatile /run/udev/hwdb.d directory but nothing actually looked at it.
2015-06-08rules: whitelist xvd* devicesAlex Crawford
Xen disks need to be whitelisted as well.
2015-06-09networkd: actually always use AddressFamilyBoolean as the bit mask it isLennart Poettering
2015-06-08build-sys: don't suppress irrelevant warningsThomas Hindoe Paaboel Andersen
We do not trigger these warnings so no need to suppress them.
2015-06-08Merge pull request #108 from phomes/masterLennart Poettering
tree-wide: remove spurious space
2015-06-08Merge pull request #110 from systemd/revert-41-ipforwardingTom Gundersen
Revert "networkd: create "kernel" setting for IPForwarding"
2015-06-08Revert "networkd: create "kernel" setting for IPForwarding"Lennart Poettering
2015-06-08tree-wide: remove spurious spaceThomas Hindoe Paaboel Andersen
2015-06-08Merge pull request #106 from teg/man-mac-randomLennart Poettering
man: systemd.link - explain random MAC addresses
2015-06-08man: systemd.link - explain random MAC addressesTom Gundersen
Two of the bits in the MAC address are set unconditioanlly, and the rest is randomized, make this clear in the documentation (as it currently read as if it was all random).
2015-06-08Merge pull request #101 from zonque/kmodLennart Poettering
kmod-setup: split warn flags
2015-06-08kmod-setup: split warn flagsDaniel Mack
Traditionally, we used to warn about ipv6 being a module or being unavailable. This was changed in b4aa82f16 ("kmod-setup: don't warn when ipv6 can't be loaded") in a way that neither of the two conditions will cause a log message. Now, while running a setup without any IPv6 is completely fine and shouldn't cause any warning, we should still warn about ipv6 being a module instead of built-in. To achieve this, split the boolean warn flag into two: one for a feature not being built-in but shipped as a module, and one to print an error when a module is entirely unavailable. We will, however, still warn if kmod returns anything else than -ENOENT in the attempt of loading the module, and at the very least, turn the message into a debug log.
2015-06-08Merge pull request #96 from haraldh/set_consumeLennart Poettering
util:bind_remount_recursive() fix "use after free"
2015-06-08util:bind_remount_recursive() fix "use after free"Harald Hoyer
set_consume(done, x) consumes x with free(x) but mount(…, x, …) uses it afterwards. coverity CID 1299006
2015-06-08Merge pull request #92 from zonque/READMELennart Poettering
README.md: add Coverity scan status badge
2015-06-08README.md: add Coverity scan status badgeDaniel Mack
2015-06-05Merge pull request #79 from zonque/fdo-87475Kay Sievers
kmod-setup: don't warn when ipv6 can't be loaded (FDO bug #87475)
2015-06-05Merge pull request #82 from gmacario/bootchart-fix-typoDaniel Mack
systemd-bootchart: Trivial typo fix in warning
2015-06-05systemd-bootchart: Trivial typo fix in warningGianpaolo Macario
Signed-off-by: Gianpaolo Macario <gmacario@gmail.com>
2015-06-05Merge pull request #80 from zonque/README.mdHarald Hoyer
Add README.md
2015-06-05Add README.mdDaniel Mack
A README.md allows us to include a badge for the current build status of Semaphore CI. Keep other information in this file minimal, and avoid information duplication but point readers to the official README.
2015-06-05bus: don't force send-masks on kdbus busesDavid Herrmann
Right now we always pass KDBUS_ITEM_ATTACH_FLAGS_RECV to KDBUS_CMD_BUS_MAKE, effectively forcing every bus connection to do the same during KDBUS_CMD_HELLO. This used to be a workaround to make sure all metadata is always present. However, we refrained from that approach and intend to make all metadata collection solely rely on /proc access restrictions. Therefore, there is no need to force the send-flags mask on newly created buses.
2015-06-05kmod-setup: don't warn when ipv6 can't be loadedDaniel Mack
Not having IPv6 is a valid setup. Let's not print a warning in that case. Addresses: https://bugs.freedesktop.org/show_bug.cgi?id=87475
2015-06-05logind: Fix user_elect_display() to be more stablePhilip Withnall
The previous implementation of user_elect_display() could easily end up overwriting the user’s valid graphical session with a new TTY session. For example, consider the situation where there is one session: c1, type = SESSION_X11, !stopping, class = SESSION_USER it is initially elected as the user’s display (i.e. u->display = c1). If another session is started, on a different VT, the sessions_by_user list becomes: c1, type = SESSION_X11, !stopping, class = SESSION_USER c2, type = SESSION_TTY, !stopping, class = SESSION_USER In the previous code, graphical = c1 and text = c2, as expected. However, neither graphical nor text fulfil the conditions for setting u->display = graphical (because neither is better than u->display), so the code falls through to check the text variable. The conditions for this match, as u->display->type != SESSION_TTY (it’s actually SESSION_X11). Hence u->display is set to c2, which is incorrect, because session c1 is still valid. Refactor user_elect_display() to use a more explicit filter and pre-order comparison over the sessions. This can be demonstrated to be stable and only ever ‘upgrade’ the session to a more graphical one. https://bugs.freedesktop.org/show_bug.cgi?id=90769
2015-06-05Merge pull request #63 from arvidjaar/issue/50Daniel Mack
fstab-generator: cescape device name in root-fsck service
2015-06-05Merge pull request #76 from crrodriguez/masterDaniel Mack
core: Remove "old kernel" warning if PR_SET_CHILD_SUBREAPER fails
2015-06-05core: Remove "old kernel" warning if PR_SET_CHILD_SUBREAPER failsCristian Rodríguez
This made sense when systemd ran on older kernels, nowdays not so much.