summaryrefslogtreecommitdiffstats
path: root/src/cgtop (unfollow)
Commit message (Collapse)AuthorFilesLines
2023-10-17tree-wide: port various parsers over to read_stripped_line()Lennart Poettering1-4/+3
2023-10-17fileio: add read_stripped_line() as trivial read_line() + strstrip() comboLennart Poettering2-0/+32
2023-10-17docs/FILE_DESCRIPTOR_STORE: NotifyAccess=cgroup -> allMike Yuan1-1/+1
Fixes #29590
2023-10-17core/mount: allow disabling stop propagation from backing deviceMike Yuan2-15/+32
With file systems that have volume management functionalities or volume managers like LVM, it's fine for the backing device of a mount to disappear after mounted. Currently, we enforce BindsTo= or StopPropagatedFrom= on the backing device, thus prohibiting such cases. Instead, let's make this configurable through x-systemd.device-bound. Closes #16801 Closes #29543
2023-10-17rules: add mtd/by-name symlinksMatthias Schiffer2-0/+13
Add persistent symlinks for MTD devices like SPI-NOR flash, based on the partition names specified on the cmdline, in a Device Tree, or by other MTD partitioning parser drivers. Using the persistent name can be preferable to using the numbered /dev/mtdX device, as the latter can change depending on probe order or when partitioning has changed.
2023-10-17meson: Fix unused format parameter warningJan Janssen1-1/+1
2023-10-16nspawn: check if we can set CoredumpReceive= before doing soNick Rosbrook1-2/+28
If systemd-nspawn is newer than the running systemd, we might try to set CoredumpReceive=yes when systemd doesn't know about it yet. Try and check if the running systemd is aware of this setting, and if not, don't try and use it. Fixes 411d8c72ec ("nspawn: set CoredumpReceive=yes on container's scope when --boot is set").
2023-10-16test: make sure that the default naming scheme name maps back to itselfZbigniew Jędrzejewski-Szmek3-10/+14
We were testing the that C constant is defined, but we weren't actually testing that the string name maps back to itself. This would catch the issue fixed by the grandparent commit. The test for the default name is moved to the test file to keep the tests together. The define is renamed to not have "_TEST" in the name. The issue here is complicated by the fact that we allow downstreams to inject additional fields, so we don't know the name of the default scheme if it not set with -Ddefault-net-naming-scheme=, so _DEFAULT_NET_NAMING_SCHEME[_TEST] is not defined in all cases, but at least in principle it could be used in other places. If it exists, it is fully valid.
2023-10-16shared/netif-naming-scheme: align tablesZbigniew Jędrzejewski-Szmek1-10/+10
2023-10-16NEWS, man: move description of SR-IOV-R net naming to v255Zbigniew Jędrzejewski-Szmek4-8/+33
https://github.com/systemd/systemd/pull/29582 adds the "v254" name. This also changes what the default is and what "latest" refers to. Without the name, the code could be enabled via runtime configuration. Nevertheless, it could be enabled at compilation time. In other words: meson setup build -Ddefault-net-naming-scheme=v254 would work, but net.naming-scheme=v254 would fail. It is possible that people were using the compile-time override, so I think we should allow "v254" scheme to stay and clearly document that it wasn't the default. Unfortunately, unless people manually introduced the compile-time override, we were never actually testing the new code too. So all the pull request testing was not useful.
2023-10-16net_id: add missing naming scheme name for v254Antonio Alvarez Feijoo1-0/+1
Follow up to 88d2bda8120dcc375a90e28b64de06b9646ab3b6
2023-10-16udev: Enable filtering the output of udevadm info --export-dbDaan De Meyer3-30/+291
Let's support the same filtering options that we also support in udevadm trigger in udevadm info to filter the devices produced by --export-db. One difference is that all properties specified by --propery-match= have to be satisfied in udevadm info unlike udevadm trigger where just one of them has to be satisfied.
2023-10-16mount-util: use mount beneath to replace previous namespace mountLuca Boccassi9-41/+109
Instead of mounting over, do an atomic swap using mount beneath, if available. This way assets can be mounted again and again (e.g.: updates) without leaking mounts.
2023-10-16update TODOLennart Poettering1-2/+0
2023-10-16run: pin the unit we invoke continously while we are runningLennart Poettering1-6/+13
We read properties of the unit, hence it shouldn't be GC'ed as long as we run. Hence, let's just set AddRef unconditionally for the units we create.
2023-10-16run: output invocation ID when starting service and scope unitsLennart Poettering2-43/+70
2023-10-16namespace: add // FIXME comments on some suplicate loggingLennart Poettering1-3/+3
@bluca thinks duplicate logging as a feature, hence simply mark these log messages as // FIXME, but don't bother.
2023-10-16 namespace: downgrade log messages to LOG_DEBUGLennart Poettering1-2/+2
almost all code in namespace.c only logs at debug level as it is "library-like" code. But there are some outliers. Adjust them to match the rest of the code (Well, there are some left)
2023-10-16namespace: don't retry to a mount if we didn't actually manage to create an ↵Lennart Poettering1-4/+5
inode
2023-10-16namespace: downgrade log message of error we ignore to LOG_WARNINGLennart Poettering1-2/+2
frankly, the log message shouldn't be there at all, but the error path be propagated up, with a recognizable error code. But apparently this is important to @bluca.
2023-10-16namespace: convert ProtectHostname= logic to a static tableLennart Poettering1-26/+17
Let's simplify things, and make them more alike handling more similar to the other ProtectXYZ= settings.
2023-10-16Add --json switch to udevadm infoDaan De Meyer3-4/+85
This allows getting the udevadm info --export-db and query "all" output as JSON.
2023-10-16namespace: normalize memory management of mount listLennart Poettering1-435/+455
So far we calculated exactly how many mounts we will generate, which is a bit fragile, and easy to get wrong. Let's normalize this, and grow the array of mounts as we need. Various other modernizations while we are at it, such as FOREACH_ARRAY usage, or `_cleanup_` usage.
2023-10-16update TODOLennart Poettering1-1/+0
2023-10-16sysext: make some calls available via varlinkLennart Poettering11-75/+593
2023-10-16stub: NULL checks for DeviceHandle and FilePathLukas1-15/+19
UKIs may be loaded in a way, that there can not be a device handle to the filesystem, that contains the image, for example when using a bootloader to load the image from a partition with a file system that is not supported by the firmware. With the current systemd stub, this causes a failed assertion, because stub gets passed a NULL DeviceHandle and FilePath. Inserting two explicit checks enables proper boot even in this case. Fixes: #29331
2023-10-16resolve: fix no mDNS announcement after probingVishal Chillara Srinivas1-1/+1
According to RFC 6762 section 8, an mDNS responder is supposed to announce its records after probing. Currently, there is a check in dns_scope_announce which returns if there are any pending transactions. This prevents announcements from being sent out even if there are pending non-probe transactions. To fix this, return only if there are active probe transactions.
2023-10-15fuzz: Add fuzzer for efi conf/osrel parsingJan Janssen2-0/+29
2023-10-15boot: Fix OOB reads in conf/osrel parsingJan Janssen2-1/+3
2023-10-15boot: Move line_get_key_value to efi-stringJan Janssen4-74/+128
No functional changes.
2023-10-15boot: Move parse_boolean to efi-stringJan Janssen6-38/+50
No functional changes.
2023-10-15test: Remove unnecessary test prefixJan Janssen6-7/+7
2023-10-15core: don't downgrade multi-state settings to booleanFrantisek Sumsal2-4/+75
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-14docs: update fuzzers docsFrantisek Sumsal1-2/+21
2023-10-14test: update Ubuntu CI instructionsFrantisek Sumsal1-3/+5
2023-10-14varlink: drop dead codeFrantisek Sumsal1-5/+1
'#' is never part of either allowed_chars or allowed_delimiters when we parse structs/enums.
2023-10-14varlink: use int for log levelFrantisek Sumsal2-5/+5
2023-10-14varlink: don't panic on malformed method definitionFrantisek Sumsal2-0/+12
2023-10-14test: add a fuzzer for the varlink IDL stuffFrantisek Sumsal3-0/+134