| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Requiring /sys/fs/bpf path to be a mount point at the moment of cgroup
controllers realization does more harm than good, because:
* Realization happens early on boot, the mount point may not be ready at
the time. That happens if mounts are made by a .mount unit (the issue we
encountered).
* BPF filesystem may be mounted on another point.
Remove the check. Instead verify that path provided by BPFProgram= is
within BPF fs when unit properties are parsed.
Split in two commits for simple backport.
|
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since commit 8d3e4ac7cd37200d1431411a4b98925a24b7d9b3 ("scope: refuse
activation of scopes if no PIDs to add are left") all "systemd-run --scope
--user" calls fail because cgroup attachments delegated to the system instance
are not counted towards successful additions. Fix this by incrementing the
return value in case unit_attach_pid_to_cgroup_via_bus() succeeds, similar to
what happens when cg_attach() succeeds directly.
Note that this can *not* distinguish the case when
unit_attach_pid_to_cgroup_via_bus() has been run successfully, but all
processes to attach are gone in the meantime, unlike the checks that commit
8d3e4ac7cd37200d1431411a4b98925a24b7d9b3 adds for the system instance. This is
because even though unit_attach_pid_to_cgroup_via_bus() leads to an internal
unit_attach_pids_to_cgroup() call, the return value over D-Bus does not include
the number of successfully attached processes and is always NULL on success.
Fixes: #21297
|
| | | |
|
|\ \ \
| | | |
| | | | |
udev: drop colon from ID_NET_NAME_MAC
|
| | | |
| | | |
| | | |
| | | | |
Fixes a bug introduced by eaba9bb3e69635d2c490c5e1b0d262b763753e1d.
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
userdbctl: add support for chaining other ssh-authorized-keys commands from userdbctl
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
And while we are at it, make 'ssh-authorized-keys' verb properly
documented. Given that OpenSSH documents the interface in its man page
it's fine to just document our implementation of it too.
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
| | |
| | |
| | | |
That way, we can reuse the call at one more place (see later patch).
|
|\ \ \
| | | |
| | | | |
network: neighbor: use "struct hw_addr_data"
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
|/ /
| |
| |
| |
| |
| | |
Follow-up for be0cc2ce6c947aafadb3f42dba405269f670b31c.
Fixes https://github.com/systemd/systemd/pull/19670#issuecomment-965817823.
|
|\ \
| | |
| | | |
hostnamed: use /proc/device-tree to get chassis type
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
From https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw
---
Userspace must not use the /sys/firmware/devicetree/base
path directly, but instead should follow /proc/device-tree
symlink. It is possible that the absolute path will change
in the future, but the symlink is the stable ABI.
---
Addresses the comment https://github.com/systemd/systemd/pull/20731#discussion_r744095262.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes a bug introduced by 0295b2fd1d97c68010c7528af13e2952886d52e0.
Fixes #21292.
|
|/ /
| |
| |
| |
| |
| | |
Otherwise the jobs will try to cancel each other out.
Follow-up to 3884837610168e6fb69fc2d5709f6c017a30beb9.
|
|\ \
| | |
| | | |
some docs/tweaks regarding porting to new archs
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
generation work on all archs that need it
This is an attempt to nudge people into sending us patches that fix
bug #14311 for us, given that the original submitter lost interest.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The discovery partitions spec so far suggested we should define
arch-specific partition type uuids only for archs that have EFI. Let's
change that and invite people to define them for any arch. Why? Even if
GPT is defined as part of the UEFI spec it's quite useful independently
of it, too. Specifically, our image dissection logic makes use of it,
i.e. systemd-nspawn, systemd-gpt-auto-generator, systemd-repart,
RootImage=, portable services, and so on. None of these tools are
related to UEFI in any way.
Hence, let's open this up.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
missing archs
Let's generate a single gcc `#warning` message asking people to define
partition type UUIDs for their architectures if they are missing.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Moving all of the gnu-efi detection into src/boot/efi/meson.build makes
more sense than having it partially split.
And thanks to subdir_done() we can simplify the code a lot.
Fixes: #21258
|
|\ \ \
| |/ /
|/| | |
ci: cancel previous jobs on ref update
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Let's save the environment (and reduce the number of jobs in GH Actions
queues) by cancelling old jobs on a ref update (force push).
See: https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#concurrency
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
This reverts commit c1036042f5aa3369d771776fb6d57fac2543d80d.
Follow-up to 0ad536c16a940b4557322f3f811db73c4b374898.
|
| |
| |
| |
| |
| | |
Also describe failure behavior more precisely in the manpage.
Fixes #20237.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Defines a "UNIT_DEPENDENCY_SLICE_PROPERTY" UnitDependencyMask type that
is used when adding slices to the dependencies hashmap. This type is
used to remove slice dependencies when they get overridden by new ones.
Fixes #20182
|
|\ \
| | |
| | | |
man: cleanups for [Match] section
|
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
Follow-up for 35896db4895f68050c3edd2c58b913dcba4e0fd8.
Fixes CID#1465796.
|
|\ \
| | |
| | | |
ether-addr-util: introduce parse_hw_addr() and related conf parsers
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|