summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* hwdb: Tag IR cameras as suchwip/hadess/webcamsBastien Nocera2021-10-275-0/+39
| | | | | | So that front-ends can ignore them if they wish to. See https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/4
* hwdb: Allow console users access to media* nodesBastien Nocera2021-10-261-0/+1
| | | | | | | | Newer webcams and video devices have controls only available through /dev/media* nodes. Make sure they're accessible in the same way as /dev/video* nodes. Closes: #21054
* change req meson versiongregzuro2021-10-261-1/+1
| | | | since `meson compile` first appears in 0.54.0
* Merge pull request #21122 from yuwata/network-optimize-reloadYu Watanabe2021-10-2612-23/+141
|\ | | | | network: slightly optimize "networkctl reload"
| * test-network: reconfigure interface instead of restarting networkdYu Watanabe2021-10-261-2/+2
| |
| * network: delay dropping addresses or so on reloading .network filesYu Watanabe2021-10-2611-18/+135
| | | | | | | | | | | | | | When a .network file is updated but its change is not so big, it is not necessary to first drop all configs and then reassign later again. This slightly optimize such situation. First foreignize all configs, and then drop later when it is not requested by the updated .network file.
| * network: rename functionYu Watanabe2021-10-262-3/+4
| |
* | homework: replace homegrown "dir-is-empty" check with dir_is_empty_at()Lennart Poettering2021-10-261-14/+5
| |
* | Merge pull request #21097 from poettering/dir-is-empty-fixYu Watanabe2021-10-265-39/+93
|\ \ | | | | | | dir_is_empty_at() tweaks
| * | tree-wide: explicitly unpoison getdents64() memoryLennart Poettering2021-10-252-0/+4
| | | | | | | | | | | | | | | | | | Apparently memory sanitizer doesn't grok getdents64() properly. Let's address that by explicitly marken memory initialized by getdents64() as unpoisoned.
| * | test: add test for dir_is_empty_at()Lennart Poettering2021-10-251-0/+32
| | |
| * | stat-util: make sure dir_is_empty_at() does something useful in all casesLennart Poettering2021-10-251-0/+6
| | |
| * | stat-util: optimize dir_is_empty_at() a bit, by using getdents64()Lennart Poettering2021-10-252-7/+19
| | | | | | | | | | | | | | | | | | That way we have a single syscall only for it, instead of the multiple readdir() and friends do. And we can operate entirely on the stack, no malloc() implicit.
| * | dirent-util: add FOREACH macro for iterating through getdents64() buffersLennart Poettering2021-10-253-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | We already have a similar loop twice, let's make it easier to read via an iteration macro. (The new macro is a bit more careful even, as it verifies the full dirent fits into the remaining buffer when returning it)
| * | dirent-util: move getdents64() related definitions to common headerLennart Poettering2021-10-252-21/+21
| | | | | | | | | | | | | | | We want to reuse getdents64() wherever necessary, let's hence move definitions useful for that into public code.
| * | stat-util: specify O_DIRECTORY when reopening dir in dir_is_empty_at()Lennart Poettering2021-10-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | That way we can fail earlier if the specified fd is not actually a directory. (Also, it's not exactly according to standards to open things without either O_RDONLY/O_RDWR...)
* | | test: enable debug logging of systemd-udevdYu Watanabe2021-10-261-0/+3
| | | | | | | | | | | | Otherwise, it is hard to debug when the test fails.
* | | network: dhcp6pd: do not assign downstream prefix when RADV is requested but ↵Yu Watanabe2021-10-264-16/+56
| | | | | | | | | | | | not configured yet
* | | network: ndisc: fix behavior when DHCPv6Client=alwaysYu Watanabe2021-10-261-20/+45
| | | | | | | | | | | | | | | The man page says that when 'always' is set, the DHCPv6 client always starts in managed mode, and that means we need to ignore the RA flags.
* | | Merge pull request #21119 from yuwata/network-dhcp6-pd-cleanupsYu Watanabe2021-10-264-81/+104
|\ \ \ | | | | | | | | network: dhcp6pd: several cleanups
| * | | network: dhcp6: rename variablesYu Watanabe2021-10-264-12/+14
| | | |
| * | | network: dhcp6pd: move logic of acquiring subnet prefix into ↵Yu Watanabe2021-10-261-43/+55
| | | | | | | | | | | | | | | | | | | | | | | | dhcp6_pd_assign_prefix() Preparation for later commits.
| * | | network: dhcp6pd: introduce a simplified and unified method to calculate ↵Yu Watanabe2021-10-261-33/+42
| | |/ | |/| | | | | | | subnet prefix
* | | libsystemd-network: do not warn when log_dhcp_client() or friends with NULLYu Watanabe2021-10-261-1/+3
| |/ |/|
* | udev: do not try to rename interface if it is already upYu Watanabe2021-10-251-0/+11
|/ | | | | | See dev_change_name() in kernel's net/core/dev.c. Fixes #21105.
* Merge pull request #21116 from poettering/test-cleanerYu Watanabe2021-10-252-5/+11
|\ | | | | make tests a bit cleaner in regards to oomd handling
| * varlink: don't try to talk to oomd from unit testsLennart Poettering2021-10-251-0/+3
| | | | | | | | | | | | | | | | Talking to external daemons we ourselves maintain is a job for the integration tests, not the unit tests. This communication is likely to fail hence don#t even bother. This makes our tests a bit cleaner.
| * cgroup: handle gracefully if we can't read oom_kill cgroup attributeLennart Poettering2021-10-251-5/+8
| |
* | Merge pull request #21117 from mrc0mmand/last-coverage-related-tweaksYu Watanabe2021-10-252-2/+25
|\ \ | | | | | | Last batch of coverage-related tweaks
| * | test: merge coverage reports from previous test runsFrantisek Sumsal2021-10-251-2/+13
| | | | | | | | | | | | Relevant mainly for tests which utilize both QEMU and nspawn.
| * | test: tweak TriggerLimitIntervalSec= when built with coverageFrantisek Sumsal2021-10-251-0/+12
| |/ | | | | | | | | | | Collecting coverage causes a significant slowdown in general, but since this test requires certain timing, we need to tweak the defaults to make it reliably pass.
* | Merge pull request #21077 from poettering/mount-setattrYu Watanabe2021-10-254-19/+90
|\ \ | | | | | | optimize remounting with mount_setattr() syscall
| * | mount-util: move opening of /proc/self/mountinfo into ↵Lennart Poettering2021-10-252-18/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | bind_remount_one_with_mountinfo() Let's move things around a bit, and open /proc/self/mountinfo if needed inside of bind_remount_one_with_mountinfo(). That way bind_remount_one() can become a superthin inline wrapper around bind_remount_one_with_mountinfo(). Main benefit is that we don't even have to open /p/s/mi in case mount_setattr() actually worked for us.
| * | mount-util: port over bind_remount_recursive_with_mountinfo() to mount_setattr()Lennart Poettering2021-10-252-1/+25
| | |
| * | mount-util: use modern mount_setattr() syscall for ↵Lennart Poettering2021-10-253-0/+51
| |/ | | | | | | | | | | | | bind_remount_one_with_mountinfo() New kernels have a nice syscall for changing bind mount flags. Let's use it. This makes the complex libmount based iteration logic unnecessary.
* | nspawn: fix build when SECCOMP is disabledYu Watanabe2021-10-251-1/+1
|/ | | | Follow-up for 20e458ae3c3b386e2b720bbd3c37d95781e69ae7.
* TODO: add note about chase_symlink flagLuca Boccassi2021-10-241-0/+3
|
* Merge pull request #21108 from mrc0mmand/here-comes-the-coverageYu Watanabe2021-10-243-6/+12
|\ | | | | A couple more coverage-related tweaks
| * test: rename the global service override file for coverage runsFrantisek Sumsal2021-10-231-1/+1
| | | | | | | | | | | | Otherwise we break TEST-15-DROPIN, since it uses /usr/lib/systemd/system/service.d/override.conf in some of its sub-tests.
| * README: fix CentOS CI badgeFrantisek Sumsal2021-10-231-1/+1
| |
| * test: disable ProtectHome= when collecting coverage as wellFrantisek Sumsal2021-10-232-5/+11
|/ | | | | | | | | | Depending on the location of the original build dir, either ProtectHome= or ProtectSystem= may get in the way when creating the gcov metadata files. Follow-up to: * 02d7e73013a92c5580023e4e548d19adbc254dbe * 6c9efba67715cd1ced170ac46c04d47934ad276a
* Merge pull request #21082 from yuwata/network-dhcp6-pd-trivial-cleanupsYu Watanabe2021-10-231-43/+53
|\ | | | | network: DHCPv6 PD: several trivial cleanups
| * network: dhcp6pd: check link state earlier before assigning prefixes to ↵Yu Watanabe2021-10-221-5/+5
| | | | | | | | | | | | downstream Also, narrow the acceptable range of the states.
| * network: dhcp6pd: also call dhcp6_pd_prepare() and dhcp6_pd_finalize() for ↵Yu Watanabe2021-10-221-8/+14
| | | | | | | | | | | | upstream interface As now the subnet prefix may be assigned to the upstream interface.
| * network: dhcp6pd: not necessary to drop routes when Assign=yesYu Watanabe2021-10-221-30/+34
| |
* | efivars: skip writing if variable is already in wanted stateAnssi Hannula2021-10-231-1/+25
| | | | | | | | | | | | | | | | | | In order to minimize EFI variable NVRAM wear, do not rewrite variables if they are already in the wanted state (i.e. same data and attributes). This allows e.g. performing repeat calls of "bootctl install" (which always rewrites the EFI boot entry) without consuming EFI NVRAM write cycles.
* | homed: don't drop caches on activationLennart Poettering2021-10-233-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | We should drop caches if we are configured to do so in all cases where we are done with home dir operations: except if that operation is activation, because in that case we are not destroying anything, but leaving it on. Hence, turn off the flag that reminds us that we should drop caches before exiting, once activation completed fully, Follow-up for 86019efa4416d7b548cab321c15bc22a65463786
* | nspawn: ignore --suppress-sync=yes when seccomp is disabledYu Watanabe2021-10-221-0/+4
| | | | | | | | | | | | Follow-up for 4a4654e0241fbeabecb8587fd3520b6b39264b9c. Fixes #21090.
* | nspawn: bump RLIMIT_NOFILE for nspawn payload similar to how host PID 1 does ↵Lennart Poettering2021-10-221-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | it for its payload We try to pass containers roughly the same rlimits as the host gets from the kernel. However, this means we'd set the RLIMIT_NOFILE to 4K. Which is quite limiting though, and is something we actually departed from in PID1: since 52d620757817bc0fa7de3ddbe43024544ced7ea0 we raise the limit substantially for all userspace. Given that nspawn is quite often invoked without proper PID1, let's raise the limits for container payloads the same way as we do from the real PID1 to its service payloads.
* | update TODOLennart Poettering2021-10-221-0/+6
| |
View Lorry Controller Status