summaryrefslogtreecommitdiffstats
path: root/man/systemd-binfmt.service.xml (unfollow)
Commit message (Collapse)AuthorFilesLines
2023-03-10meson: Introduce userspace depJan Janssen18-178/+373
This will help in a later commit to separate userspace from EFI builds.
2023-03-10socket-util: fix socket_get_family()Lennart Poettering3-21/+17
Function didn't actually return anything useful. Quite a shame.
2023-03-10repart: Add support for reading mkfs options from environmentDaan De Meyer5-23/+48
2023-03-10load-fragment: add user credential specifiers to user.confRonan Pigott3-3/+43
This enables the ManagerEnvironment= settings in the user's user.conf to reference some user data like $HOME for the purpose of setting environment variables derived from these values.
2023-03-09data-fd-util: use fd_reopen() a bit moreLennart Poettering1-4/+3
2023-03-09fd-util: move ACQUIRE_NO_XYZ flags to the header the function using them is inLennart Poettering2-9/+9
Follow-up for: b25a930f0e2ebe77bc8b0f0acfac8a3b27ef1f0a
2023-03-09mempress: change default PSI window duration to 2sLennart Poettering5-7/+9
This changes the PSI window duration we default to for watching memory pressure events from 1s to 2s. This is because apparently the kernel will soon disallow window durations other than 2s for unprivileged processes. Hence, we'll bump the threshold from 100m to 200ms, and the window from 1s to 2s.
2023-03-09update TODOLennart Poettering1-3/+6
2023-03-09test: test new systemd-dissect --attach/--detach/--loop-ref= and /dev/loop/* ↵Lennart Poettering1-0/+22
symlinks Let's test that everything we just added works in combination.
2023-03-09mountpoint-util: add comment explaining why fstype_can_discard() can't use ↵Lennart Poettering1-3/+5
mount_option_supported()
2023-03-09mountpoint-util: add new fstype_can_umask() helperLennart Poettering4-1/+22
2023-03-09mountpoint-util: move 'norecovery' detection into its own helper callLennart Poettering4-1/+25
And let's also ask the kernel explicitly for support.
2023-03-09mountpoint-util: use mount_option_supported() to detect if 'discard' is ↵Lennart Poettering2-0/+15
support for an fs
2023-03-09mountpoint-util: generalize mount_option_supported()Lennart Poettering4-23/+80
2023-03-09gpt-auto-generator: port to partition_pick_mount_options() tooLennart Poettering1-24/+59
This way we'll have the same mount options in place if we boot via the gpt generator, or if we mount a DDI locally. Note that this will also enable MS_NOSYMFOLLOW on ESP and XBOOTLDR now, if booted via gpt-auto-generator.
2023-03-09dissect-image: set MS_NOSYMFOLLOW for ESP/XBOOTLDRLennart Poettering2-40/+111
When we mount a DDI, let's set MS_NOSYMFOLLOW for ESP/XBOOTLDR. They are generally untrusted territory, (i.e. outside of encryption/authentication via dm-crypt/dm-verity). Moreover they are generally FAT, where symlinks don't exist anyway. Let's hence disable symlinks for them. This slightly refactors how we put together mount options for mounts, splitting this out into a new helper call dissected_partition_pick_options(), which we should be able to reuse later in gpt-auto-generator, to ensure mounts via loopback as DDI and those on bare metal get the same options.
2023-03-09tpm2: add tpm2_pcr_read()Dan Streetman1-40/+89
2023-03-09test/test-tpm2: add tests for pcr selection functionsDan Streetman1-0/+342
2023-03-09tpm2: add/rename functions to manage pcr selectionsDan Streetman5-71/+358
This renames some functions to match other to/from_string() naming, and allows better management of TPML_PCR_SELECTION and TPMS_PCR_SELECTION structs.
2023-03-09tpm2: add TPM2_PCR_VALID()Dan Streetman4-9/+15
2023-03-09tpm2: add tpm2_get_policy_digest()Dan Streetman1-42/+57
2023-03-09test/test-bitfield: add tests for bitfield macrosDan Streetman2-0/+228
2023-03-09udev: add /dev/loop/ symlinksLennart Poettering1-0/+11
This adds symlinks that allow accessing loopback block devices via stable names that reference their backing block devices, make the unpredictable naming of loopback devices less of an issue. Example: 1. Create a loopback block device for a file $F losetup --find $F 2. Reference the backing block device via its inode: L="$(stat -c '/dev/loop/by-inode/%Hd:%Ld-%i' $F)" fdisk $L In the above the loop device name (which might be /dev/loop47 or any other name) is not used at all.
2023-03-09dissect: shorten code a bitLennart Poettering1-10/+4
2023-03-09dissect: allow setting "lo_file_name" field of loopback block devicesLennart Poettering2-0/+44
When attaching a loopback file this allows us to set an explicit name for it. This is useful since it allows a caller to pre-select a string that is directly attached to the loopback file. Via udev rules we'l later make the device accessible through this name. Note that "lo_file_name" is supposed to carry a file name of the backing file, but the kernel actually does not care or enforce any of that, it just stores the filename and returns it later. This makes it so useful, as userspace has total control of that field. "lo_file_name" should not be confused with the sysattr "loop/backing_file" which is actually maintained by the kernel itself, and always shows the file to the backing inode without userspace having direct control over the returned string. Because the sysattr is generated by the kernel it is subject to file system namespacing and everything, while "lo_file_name" is not, it's really just a string passed through the kernel.
2023-03-09dissect: add commands for attaching/detaching loopback devicesLennart Poettering2-0/+171
Sometimes it is useful attaching DDIs without mounting them. We could use "losetup" for that, but doing this in systemd-dissect has various benefits: 1. we superficially validate the DDI first 2. we set the sector size depending on what we determine 3. we synchronously create the per-partition block devices
2023-03-09loop-util: add API for selecting "lo_file_name" field for a loopback deviceLennart Poettering2-0/+36
2023-03-09loop-util: add call for setting the autoclear flag at arbitrary timesLennart Poettering2-0/+21
2023-03-09loop-util: keep track of inode/devnum of backing fileLennart Poettering2-3/+13
2023-03-09udev-builtin-blkid: pick up info of backing fileLennart Poettering1-0/+108
This adds support for retrieving info about the inode backing a loopback file to udev-builtin-blkid. It will pick up the inode number and device of the backing inode, as well as the lo_file_name[] array that the loopback device maintains. A later patch uses this information to create block device symlinks in /dev/ that allow refering block devices by their backing inodes. This is useful when separate tools set up a loopback device from those which ultimately shall mount them, and there shall be a stable reference be passed along. For example, we can add a new kernel option setuploop= or so which allows setting up a block device via a generator, and still have a way to safely reference later. And yes, this doesn't directly have anything to do with the probing libblkid does, but it's close enough, and we have the device open anyway here, so the additional ioctl() here should not hurt.
2023-03-09udev: add new udev_builtin_add_propertyf() helperLennart Poettering2-0/+21
2023-03-09dissect: add new helper dissected_partition_fstype()Lennart Poettering2-1/+7
Initially we only have one user, but following patches will add more.
2023-03-09mountpoint-util: add helper that checks if MS_NOSYMFOLLOW is supportedLennart Poettering3-0/+68
2023-03-09missing: add more defines to fsopen() definitionsLennart Poettering1-0/+12
2023-03-09missing: add fsmount() syscall fallback definitionLennart Poettering2-0/+21