8 Commits

Author	SHA1	Message	Date
Frantisek Sumsal	72d50da4f6	test: skip SocketBind*= tests when built without a bpf framework ... The test intentionally checks for -BPF_FRAMEWORK so we run the test case (and fail) even if we rename the feature flag.	2023-10-31 17:36:03 +01:00
Yu Watanabe	d19434fbf8	tree-wide: fix typo	2023-10-31 14:35:33 +09:00
Luca Boccassi	7b6d3dcdd2	exec-invoke: don't double-close FDs on error ... When a late error occurs in sd-executor, the cleanup-on-close of the context structs happen, but at that time all FDs might have already been closed via close_all_fds(), so a double-close happens. This can be seen when DynamicUser is enabled, with a non-existing WorkingDirectory. Invalidate the FDs in the context structs if close_all_fds succeeds.	2023-10-28 16:56:25 +02:00
Luca Boccassi	3ad5aedadc	test: io.latency cgroup support might not be available, skip test ... It doesn't seem to be enabled on Debian stable, and the test fails. Follow-up for 5efc8183c9	2023-10-28 08:08:42 +00:00
Frantisek Sumsal	5efc8183c9	test: cover more sd-executor related stuff ... Let's probe directives that have slightly more "complex" handling in the serialization/deserialization machinery.	2023-10-27 21:01:33 +02:00
Luca Boccassi	63862de4b7	core: do not post-process skipped mounts ... When a mount is gracefully skipped (e.g.: BindReadOnlyPaths=-/nonexistent) we still post-process it, like making it read-only. Except if nothing has been mounted, the mount point will be made read-only for no reason. Track when mounts are skipped and avoid post-processing. One day we'll switch all of this to the new mount api and do these operations atomically or not at all. Fixes https://github.com/systemd/systemd/issues/29725	2023-10-26 21:15:41 +01:00
Frantisek Sumsal	e98f7f9122	test: skip Protect{Home,System}= tests with coverage builds ... With coverage builds we disable Protect{Home,System}= via a service.d dropin in /etc, which has, unfortunately, higher priority than our transient systemd-run stuff. Let's just skip the affected tests in that case instead of making the test setup even more complicated.	2023-10-19 18:03:57 +01:00
Frantisek Sumsal	abcf59970d	core: don't downgrade multi-state settings to boolean ... Protect{Home,System,Proc,Subset}= are not booleans, so make sure we use the intended value instead of just true/false. See: https://github.com/systemd/systemd/pull/29552 Follow-up to: 79d956d	2023-10-15 14:04:28 +08:00