summaryrefslogtreecommitdiffstats
path: root/LICENSE.LGPL2.1 (unfollow)
Commit message (Collapse)AuthorFilesLines
2019-02-06core/dbus-service: write PIDFile= setting to transient unit fileYu Watanabe1-2/+6
Follow-up for a9353a5c5b512f107955e56a9812724f40b841d3.
2019-02-06core/load-fragment: empty assignment to PIDFile= resets the valueYu Watanabe1-0/+6
Follow-up for a9353a5c5b512f107955e56a9812724f40b841d3.
2019-02-06test-network: ignore tunnel devices automatically added by kernelYu Watanabe1-1/+1
Fixes #10934.
2019-02-06test-network: check port range and ipproto attributes are supported by ↵Yu Watanabe1-0/+24
kernel and ip command
2019-02-05udevadm info: "-a" should enumerate sysfs attributes, not envs (#11642)Mantas Mikulėnas1-1/+4
This fixes a bug introduced by 13aca847695f49afeb93367ecdad76035fa6c139.
2019-02-04analyze security: fix recursive call of syscall_names_in_filter()Yu Watanabe1-11/+11
When `syscall_names_in_filter()` is called in itself, it is already examined with `whitelist`. Or, in other words, `syscall_names_in_filter()` returns bad or good in boolean. So, the returned value should not be compared with `whitelist` again. This replaces #11302.
2019-02-04portable: document /etc/machine-id and /etc/resolv.confДамјан Георгиевски1-4/+8
… requirement for portable service images. systemd will mount the host machine-id and resolv.conf at these locations, so for read-only images these must exist in the image, because they can't be created.
2019-02-04hwdb: Add support for Gemini NC14 keyboardJonathan McDowell1-0/+7
2019-02-04machinectl: fix argument index in error logYu Watanabe1-2/+2
Fixes #11628.
2019-02-04NEWS fix boolean value for meson optionsChristian Hesse1-1/+1
Valid boolean values for meson are 'true' and 'false', not 'yes' and 'no'.
2019-02-03hwdb: Add key-mapping for GPIO-keys on HP stream 7 tablet (#11631)Hans de Goede1-0/+8
The HP stream 7 ACPI tables contains a gpio-keys entry for a non connected GPIO causing spurious events, this commit maps this key to unknown to disable it. BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=202279
2019-02-03Add another entry for MX Master to 70-mouse.hwdb (#11633)Claudius Ellsel1-0/+1
2019-02-03networkd-dhcp6.c: fix build without IFA_F_NOPREFIXROUTEFabrice Fontaine1-0/+1
systemd fails to build on kernel without IFA_F_NOPREFIXROUTE since 9714c02 So put include missing_network.h Fixes: - http://autobuild.buildroot.org/results/970b09e1d49b53dff12a07ca4ad424ef9dd29a69 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
2019-02-03networkd-address.c: fix build without IFA_F_NOPREFIXROUTEFabrice Fontaine1-0/+1
systemd fails to build on kernel without IFA_F_NOPREFIXROUTE since 9714c02 So put include missing_network.h Fixes: - http://autobuild.buildroot.org/results/970b09e1d49b53dff12a07ca4ad424ef9dd29a69 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
2019-02-03networkd-ndisc.c: fix build without IFA_F_NOPREFIXROUTEFabrice Fontaine1-0/+1
systemd fails to build on kernel without IFA_F_NOPREFIXROUTE since 9714c02 So put include missing_network.h Fixes: - http://autobuild.buildroot.org/results/970b09e1d49b53dff12a07ca4ad424ef9dd29a69 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
2019-02-03networkd-brvlan.c: fix build without BRIDGE_VLAN_INFO_RANGE_ENDFabrice Fontaine1-0/+1
systemd fails to build on kernel without BRIDGE_VLAN_INFO_RANGE_END since 9714c02 So put include missing_if_bridge.h Fixes: - http://autobuild.buildroot.org/results/970b09e1d49b53dff12a07ca4ad424ef9dd29a69 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
2019-02-03travis: stop using the official upstream-systemd-ci repositoryEvgeny Vereshchagin1-1/+2
Turns out the key for the repository hasn't been propagated properly so let's restore the kludge that was removed in https://github.com/systemd/systemd/pull/11582. Of course it's ugly but at least it works. The issue was kind of reported to the maintainers of the repository in https://github.com/systemd/systemd/pull/11531#issuecomment-460023474.
2019-02-03test-network: add or drop whitespaceYu Watanabe1-3/+3
2019-02-03test-network: fix test_dhcp_server() and test_ipv6_prefix_delegation()Yu Watanabe1-1/+1
The tests have been broken since 30d3b54ebad41082e99cabbee815cb113aa0b5c4.
2019-02-02shared: Revert commit 49fe5c099 in parts for function parse_acl.YmrDtnJu1-4/+4
Too much code has been removed while replacing startswith with STARTSWITH_SET so that every ACL specified e.g. in tmpfiles.d was parsed as a default ACL.
2019-02-02test: (ArchLinux) Replace initramfs-linux.img with initramfs-linux-fallback.img.Taro Yamada1-1/+1
Currently /boot/initramfs-linux.img is used as the default initrd for ArchLinux. Although, since the kernel modules that are not necessary for the host environment are removed from initramfs-linux.img by mkinitcpio 's autodetect hook, the kernel modules necessary for qemu may be missing. (ata_piix, ext4, and so on in my case.) As a result, the test environment may not be built properly and the test will be failed. initramfs-linux-fallback.img will skip this autodetect hook, so the test will run successfully in more environments. Both initramfs-linux.img and initramfs-linux-fallback.img are generated by default.
2019-02-01test-execute: unset $HOME before testingYu Watanabe1-0/+1
Otherwise, test for %h specifier may fail. Fixes #11609.
2019-02-01man: add referecne to systemd-system.confYu Watanabe7-0/+7
2019-02-01man: clarify the source of DefaultTimeoutStartSec=Yu Watanabe1-3/+4
2019-02-01man: fix volume num of journalctlYu Watanabe2-2/+2
2019-01-31pager: improve english a bitLennart Poettering1-2/+2
2019-01-31Add Lenovo Yoga 500-14IBD, 80N4 GlidePoint Touchpad (#11606)govwin1-0/+7
Touchpad size as listed by kernel was 102x28mm. Update changes it to 106x71mm. User measured (actual size): 108x72mm.
2019-01-30More NEWS prep for v241v241-rc2Lennart Poettering1-2/+34
2019-01-30test-network: skip erspan test if not availableSusant Sahani1-0/+12
2019-01-30Fixed minor typo in man/tmpfiles.d.xmlRonnie P. Thomas1-1/+1
2019-01-30tests: crash PID1 if UBSan is unhappyEvgeny Vereshchagin1-2/+2
Now that https://github.com/systemd/systemd/issues/10332 is unlikely to happen it should be totally fine to try to crash PID1 :-)
2019-01-30tests: ignore memory leaks in dbus-daemonEvgeny Vereshchagin1-7/+15
Otherwise, the test fails on Fedora 28 with ``` Jan 30 01:42:35 systemd-testsuite dbus-daemon[61]: [system] Successfully activated service 'org.freedesktop.systemd1' Jan 30 01:42:35 systemd-testsuite systemd[61]: dbus.service: Kernel keyring access prohibited, ignoring. Jan 30 01:42:35 systemd-testsuite systemd[61]: dbus.service: Executing: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only Jan 30 01:42:50 systemd-testsuite dbus-daemon[61]: ================================================================= Jan 30 01:42:50 systemd-testsuite dbus-daemon[61]: ==61==ERROR: LeakSanitizer: detected memory leaks Jan 30 01:42:50 systemd-testsuite dbus-daemon[61]: Direct leak of 72 byte(s) in 1 object(s) allocated from: Jan 30 01:42:50 systemd-testsuite dbus-daemon[61]: #0 0x7f21f9e29088 in __interceptor_realloc (/usr/lib64/libasan.so.5+0xef088) Jan 30 01:42:50 systemd-testsuite dbus-daemon[61]: #1 0x7f21f9b1b23c (/lib64/libdbus-1.so.3+0x3323c) Jan 30 01:42:50 systemd-testsuite dbus-daemon[61]: #2 0x240000001b (<unknown module>) Jan 30 01:42:50 systemd-testsuite dbus-daemon[61]: Direct leak of 16 byte(s) in 1 object(s) allocated from: Jan 30 01:42:50 systemd-testsuite dbus-daemon[61]: #0 0x7f21f9e29088 in __interceptor_realloc (/usr/lib64/libasan.so.5+0xef088) Jan 30 01:42:50 systemd-testsuite dbus-daemon[61]: #1 0x7f21f9b1b23c (/lib64/libdbus-1.so.3+0x3323c) Jan 30 01:42:50 systemd-testsuite dbus-daemon[61]: #2 0x7ffffffff (<unknown module>) Jan 30 01:42:50 systemd-testsuite dbus-daemon[61]: SUMMARY: AddressSanitizer: 88 byte(s) leaked in 2 allocation(s). ``` The leaks were reported and fixed in https://bugs.freedesktop.org/show_bug.cgi?id=107320.
2019-01-29travis: switch to the "official" systemd-ci repositoryEvgeny Vereshchagin1-3/+1
Now that add-apt-repository hasn't failed for almost two days on Semaphore it should be safe to assume that the key has been propagated properly and the repository is ready to be used on Travis CI.
2019-01-29test-network: set missing prefixlenYu Watanabe3-4/+4
2019-01-29network: warn if Address= is specified without prefixlenYu Watanabe1-1/+9
This is the first step for #11307.
2019-01-29util: add a new mode for in_addr_prefix_from_string_auto_internal() which ↵Yu Watanabe4-91/+92
refuses address without prefixlen This also drops in_addr_default_prefix_from_string(), as it is only used by test-in-addr.
2019-01-29Add a warning about the difference in permissions between existing ↵Taro Yamada1-2/+15
directories and unit settings. To follows the intent of 30c81ce, this change does not execute chmod() and just add warnings.
2019-01-28units: make sure initrd-cleanup.service terminates before switching to rootfsFranck Bui1-1/+1
A follow-up for commit a8cb1dc3e0fa81aff. Commit a8cb1dc3e0fa81aff made sure that initrd-cleanup.service won't be stopped when initrd-switch-root.target is isolated. However even with this change, it might happen that initrd-cleanup.service survives the switch to rootfs (since it has no ordering constraints against initrd-switch-root.target) and is stopped right after when default.target is isolated. This led to initrd-cleanup.service entering in failed state as it happens when oneshot services are stopped. This patch along with a8cb1dc3e0fa81aff should fix issue #4343. Fixes: #4343
2019-01-28test-barrier: skip the test in virtualized/containerized environmentsFrantisek Sumsal1-0/+17
2019-01-28network/wireguard: use sd_netlink_message_append_sockaddr_in{,6}()Yu Watanabe1-2/+2
2019-01-28sd-netlink: introduce sd_netlink_message_append_sockaddr_in{,6}()Yu Watanabe4-1/+40
2019-01-28test-network: add more checks in NetworkdNetDevTests.test_wireguardYu Watanabe2-1/+12
2019-01-28network/wireguard: fixes sending wireguard peer settingsYu Watanabe1-1/+1
This fixes a bug introduced by e1f717d4a02e15ae11a191dd4962b2f4d117678d. Fixes #11579.
2019-01-27kernel-install: fix dracut initrd detection (240 backward compatibility) ↵Marc-Antoine Perennou2-4/+12
(#11570) * kernel-install: fix initrd when called as installkernel Running make install from the kernel runs e.g.: installkernel 4.20.5 arch/x86/boot/bzImage System.map "/boot" Since 0912c0b80eb24fb9a4e1cc4abf274a1358b9943d this would cal 90-loaderentry.install with those arguments: add 4.20.5 /boot/... arch/x86/boot/bzImage System.map "/boot" The two last arguments would then be handled as the initrd files. As System.map exists in current directory but not in /boot/... it would get copied there, and used as initrd intead of the initrd which has been generated by dracut. With this change, nothing changes when kernel-install is called directly, but when it's called as installkernel, we now pass thos arguments to 90-loaderentry.install: add 4.20.5 /boot/... arch/x86/boot/bzImage initrd initrd is thus detected as the file to use for the initrd, and as it exists, nothing is copied over and the initrd line generated is consistent with what one would expect * kernel-install: fix dracut initrd detection when called directly This brings back the systemd 240 behaviour when called directly too * kernel-install: unify initrd fallback * kernel-install: move initrd fallback handling to 90-loaderentry.install * kernel-install: move initrd fallback just before creating loader entry
2019-01-27Revert "Fixes #11128"Taro Yamada1-8/+2
This reverts commit 0bf05f0122f0f13cd0c0bc35a31861875d2ead31 because it breaks 30c81ce. Please see #11540.
2019-01-26tree-wide: use newa() instead of alloca() wherever we canLennart Poettering13-20/+22
Typesafety is nice. And this way we can take benefit of the new size assert() the previous commit added.
2019-01-26alloc-util: whenever any of our alloca() wrappers is used to allocate overly ↵Lennart Poettering1-17/+32
large memory blocks, hit an assert() Of course, this should never happen, but let's better be safe than sorry, and abort rather than continue when a too large memory block is allocated, simply asa safety precaution. An early abort is better than continuing with a likely memory corruption later.
2019-01-26build-sys: bump package/library versionsv241-rc1Zbigniew Jędrzejewski-Szmek1-3/+3
We added sd_bus_close_unref().
2019-01-26pid1: fix cleanup of stale implicit deps based on /proc/self/mountinfoZbigniew Jędrzejewski-Szmek1-1/+6
The problem was introduced in a37422045fbb68ad68f734e5dc00e0a5b1759773: we have a unit which has a fragment, and when we'd update it based on /proc/self/mountinfo, we'd say that e.g. What=/dev/loop8 has origin-fragment. This commit changes two things: - origin-fragment is changed to origin-mountinfo-implicit - when we stop a unit, mountinfo information is flushed and all deps based on it are dropped. The second step is important, because when we restart the unit, we want to notice that we have "fresh" mountinfo information. We could keep the old info around and solve this in a different way, but keeping stale information seems inelegant. Fixes #11342.
2019-01-26units: drop conditionalization of systemd-tmpfiles-setup-dev.serviceLennart Poettering1-1/+0
Currently, tmpfiles runs in two separate services at boot. /dev is populated by systemd-tmpfiles-setup-dev.service and everything else by systemd-tmpfiles-setup.service. The former was so far conditionalized by CAP_SYS_MODULES. The reasoning was that the primary purpose of populating /dev was to create device nodes based on the static device node info exported in kernel modules through MODALIAS. And without the privs to load kernel modules doing so is unnecessary. That thinking is incomplete however, as there might be reason to create stuff in /dev outside of the static modalias usecase. Thus, let's drop the conditionalization to ensure that tmpfiles.d rules are always executed at least once under all conditions. Fixes: #11544