summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Finalize NEWS and meson.version for v257v257Luca Boccassi2024-12-102-3/+3
|
* Chores for v257 (#35525)Luca Boccassi2024-12-1013-136/+1105
|\
| * NEWS: update list of contributorsLuca Boccassi2024-12-101-17/+19
| |
| * Update hwdbLuca Boccassi2024-12-107-119/+1058
| | | | | | | | ninja -C build update-hwdb
| * test: skip TEST-13-NSPAWN.nspawn/machined, TEST-86-MULTI-PROFILE-UKI and ↵Luca Boccassi2024-12-103-0/+3
| | | | | | | | | | | | | | | | TEST-07-PID1.private-pids.sh These new tests are flaky, so disable them temporarily, until after the release, to avoid pushing out new flakiness to consumers. They will be re-enabled immediately after.
| * test: add TEST_SKIP_SUBTESTS/TEST_SKIP_TESTCASESLuca Boccassi2024-12-102-0/+25
| | | | | | | | Inverse of the TEST_MATCH_SUBTEST/TEST_MATCH_TESTCASE variables
* | copy: do not try to copy zero size dataYu Watanabe2024-12-101-0/+2
| | | | | | | | | | | | | | | | | | | | Hopefully fixes the following sanitizer issue: === [ 3754.797377] systemd-journald[776]: ../src/src/shared/copy.c:463:37: runtime error: variable length array bound evaluates to non-positive value 0 [ 3755.101713] systemd-journald[776]: Received SIGTERM from PID 1 (systemd). [ 3755.124580] systemd-journald[776]: Journal stopped Found 1 sanitizer issues (0 internal, 0 asan, 0 ubsan, 0 msan). ===
* | TEST-07-PID: wait for sleep command being executed by sd-executorYu Watanabe2024-12-101-1/+1
| | | | | | | | Hopefully fixes #35528.
* | sd-varlink: add function to configure server object info (#35519)Luca Boccassi2024-12-1026-65/+162
|\ \ | |/ |/|
| * sd-varlink: modernize pointer style in function signaturesZbigniew Jędrzejewski-Szmek2024-12-102-6/+6
| |
| * various: set info on varlink server objectZbigniew Jędrzejewski-Szmek2024-12-1021-48/+107
| | | | | | | | | | | | The values that were previously hardcoded in sd-varlink.c are now defined in new varlink_set_info_systemd() and that function is called everywhere where we create a server.
| * sd-varlink: add sd_varlink_server_set_infoZbigniew Jędrzejewski-Szmek2024-12-105-11/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | Fixes https://github.com/systemd/systemd/issues/35508. As reported in the bug, the values were hardcoded for the systemd project. https://varlink.org/Service lists vendor, product, version, url, and interfaces as the mandatory parameters, so add an interface to set the first four. The last field is set automatically based on the registered interfaces as before. If the values are not filled in, we return empty strings. With NULL, 'varlinkctl info' would say: (string):1:25: Object field 'vendor' has wrong type null, expected string.
* | Cryptenroll pager and tweaks (#35517)Luca Boccassi2024-12-104-15/+29
|\ \
| * | cryptsetup: add debug messageZbigniew Jędrzejewski-Szmek2024-12-101-1/+3
| | |
| * | cryptenroll: show which devices support "hmac secret"Zbigniew Jędrzejewski-Szmek2024-12-102-6/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We'd silently skip devices which don't have the feature in the list. This looked wrong esp. if no devices were suitable. Instead, list them and show which ones are usable. $ build/systemd-cryptenroll --fido2-device=list PATH MANUFACTURER PRODUCT HMAC SECRET /dev/hidraw7 Yubico YubiKey OTP+FIDO+CCID ✓ /dev/hidraw10 Yubico Security Key by Yubico ✗ /dev/hidraw5 Yubico Security Key by Yubico ✗ /dev/hidraw9 Yubico Yubikey 4 OTP+U2F+CCID ✗
| * | cryptenroll: advertise device autodetection and listingZbigniew Jędrzejewski-Szmek2024-12-091-6/+6
| | |
| * | systemd-cryptenroll: drop unnecessary {}Zbigniew Jędrzejewski-Szmek2024-12-091-2/+1
| | |
| * | systemd-cryptenroll: use pager for --help, add --no-pager optionZbigniew Jędrzejewski-Szmek2024-12-092-0/+12
| |/
* | test: use mkdir -p in TEST-25-IMPORTLuca Boccassi2024-12-101-3/+3
| | | | | | | | | | | | | | [ 15.896174] TEST-25-IMPORT.sh[473]: + mkdir /var/tmp/scratch [ 15.902524] TEST-25-IMPORT.sh[519]: mkdir: cannot create directory ‘/var/tmp/scratch’: File exists https://github.com/systemd/systemd/actions/runs/12248114409/job/34167155679?pr=35520
* | Update syscall tables (#35520)Zbigniew Jędrzejewski-Szmek2024-12-1021-0/+84
|\ \
| * | seccomp-util: add getxattrat and friendsYu Watanabe2024-12-101-0/+4
| | | | | | | | | | | | | | | The new syscalls are added in kernel-6.13: https://github.com/torvalds/linux/commit/6140be90ec70c39fa844741ca3cc807dd0866394
| * | basic: update syscall tablesYu Watanabe2024-12-1020-0/+80
| | |
* | | hostnamectl: respect SYSTEMD_COLORSSebastian Gross2024-12-101-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of the wrapper functions the color defines where used directly. This was especially a problem for ANSI_HIGHLIGHT_YELLOW which is not legible at all for light themes such as solarized. The 16 color palette fallback can be set to a sane yellow or orange on that matter but it was not used though `SYSTEMD_COLORS=16` was set. Use the proper wrapper functions and let the right color be selected the way other components do it already.
* | | mkosi: several improvements for running with sanitizers (#35480)Yu Watanabe2024-12-1010-25/+187
|\ \ \ | |/ / |/| |
| * | test: use systemd-asan-env environment file at more placesYu Watanabe2024-12-103-14/+29
| | |
| * | test-network: check status of networkd after everything cleared on tear downYu Watanabe2024-12-101-5/+16
| | | | | | | | | | | | | | | | | | Otherwise, if networkd is failed, e.g. .network files that triggered the failure will remain, and the next test case will start with previous .network files. So, most subsequent test will fail.
| * | mkosi/sanitizers: add more ASAN optionsYu Watanabe2024-12-102-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | This adds the following three options: - detect_invalid_pointer_pairs=2 - handle_ioctl=1 - print_cmdline=1 Note, these options were used in the CentOS CI job.
| * | test: extract sanitizer reports from journalYu Watanabe2024-12-103-2/+137
| | |
| * | mkosi: move drop-in config for sanitizersYu Watanabe2024-12-101-0/+0
|/ /
* | Revert "test: tentatively disable SELinux tests"Yu Watanabe2024-12-092-4/+5
| | | | | | | | This reverts commit 261a3d191ed53498e7672ad4da5936a881866088.
* | hwdb: Add Chuwi MiniBook X trackpad fuzzGreg Heartsfield2024-12-091-0/+9
| | | | | | | | | | This adds X/Y fuzz for the Chuwi MiniBook X trackpad. There is significant trackpad jitter without this setting applied.
* | mkosi: Use rawhide tools tree in CIDaan De Meyer2024-12-091-0/+1
|/ | | | | | To build rawhide images we might need more recent tools from rawhide itself. While Arch would generally be up-to-date enough as well, it doesn't provide the selinux tools so we use Fedora Rawhide instead.
* journalctl: show coredumps again when --unit= is specifiedYu Watanabe2024-12-093-17/+65
| | | | | | | | | | | | | | | | This is a revised version of cbd5f5d7d6d652d52a18170123f5d08baf7e9862, which is reverted by 560412148fa62d779ea522d43960dd3acd44b261. The filter condition for _UID= field was added by fdcd37df3b97abc381c7b7a29b81cc013c7a3230. However, after 888e378da2dbf4520e68a9d7e59712a3cd5a830f, coredumps for system services are stored by systemd-coredump user. Hence, _UID=0 does not match anything anymore. When we are reading the system journal, let's set _UID=<systemd-coredump>, then we can show coredumps for system services again. When we are reading an external journal, then the uid of systemd-coredump may be different from the one on the current system, so let's drop the filter condition for _UID= in that case.
* systemctl: use correct runtime scopeLennart Poettering2024-12-091-1/+1
|
* boot: exclude the trailing padding from initrd size in initrd_prepare()Zbigniew Jędrzejewski-Szmek2024-12-091-4/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a follow-up for f8fa4222c9ac3e74e91c64e25e9532c99559cf99 (boot: Make initrd_prepare() semantically equivalent to combine_initrds()). That commit changed the way that the initrd is prepared for type#1 boot loader entries, also effectively rounding up the sizes to a multiple of 4. In [1], downstream packagers report that the trailing zeroes result in the calculated hash being different. To restore compatibility with previous hash calculations and signatures, change the reported size by excluding the trailing padding. This should restore the calculation results for the case where only one initrd is used. This patch doesn't touch the stub, i.e. doesn't change behaviour for UKIs. The seems fine, since we didn't change that recently, so any changes there would break compatiblity. The measurement results for type#1 and type#2 entries are generally going to be different anyway. ukify and systemd-measure are also out of scope here, because they are for UKIs. Fixes https://github.com/systemd/systemd/issues/35439. The other changes to the way the initrd is constructed are kept, so hopefully the original issue with booting in qemu is not recreated. [1] https://bugzilla.suse.com/show_bug.cgi?id=1233752 My simple test: I'm booting a QEMU VM with systemd-boot and a type#1 entry. With old systemd-boot: $ sudo systemd-pcrlock log | grep 'kernel-initrd.*event-tag' 9 █ kernel-initrd event-tag - a337a8321bf81de5c53a842843e8f9a926f73a676e5620ff76df94d1c66bc931 F - Linux: kernel command line 9 █ kernel-initrd event-tag - aec1aee5358bde36f5498f2dc243dec2b103f81242de57b887a11f53677f1272 F - Linux: initrd With updated systemd-boot: $ sudo systemd-pcrlock log | grep 'kernel-initrd.*event-tag' 9 █ kernel-initrd event-tag - a337a8321bf81de5c53a842843e8f9a926f73a676e5620ff76df94d1c66bc931 F - Linux: kernel command line 9 █ kernel-initrd event-tag - 3ccaa710304aef8734a20265ea7fd3dd67d5461c6b3309c6d30d5c7d2a3ae7f9 F - Linux: initrd This matches the initrd hash: $ sudo sha256sum /efi//26f948d2082e4ae89f5a3af351b63149/6.12.0-rc4+/initrd-dracut 3ccaa710304aef8734a20265ea7fd3dd67d5461c6b3309c6d30d5c7d2a3ae7f9 /efi//26f948d2082e4ae89f5a3af351b63149/6.12.0-rc4+/initrd-dracut
* mkosi: various improvements (#35491)Daan De Meyer2024-12-0810-45/+40
|\
| * mkosi: Set meson --max-lines= to 300 in CIDaan De Meyer2024-12-081-1/+2
| | | | | | | | | | | | By default meson only shows the last 100 lines of output for failed tests. Let's bump this to 300 with the new --max-lines= option I added so we get more useful output on test failures.
| * mkosi: Use mkosi sandbox in CI with Fedora tools treeDaan De Meyer2024-12-081-35/+18
| | | | | | | | | | This gives us a newer meson which will allow us to use the new --max-lines= feature I added in meson 1.5.0.
| * test: Set kernel loglevel to INFO when running tests unattendedDaan De Meyer2024-12-081-0/+1
| | | | | | | | | | | | | | This makes sure all kernel log messages are logged to the console. This should be helpful during shutdown to detect possible issues with journald when the logs can't be written to the journal itself anymore but are written to kmsg.
| * mkosi: Move leak sanitizer supressions file to sanitizers extra treeDaan De Meyer2024-12-081-0/+0
| |
| * mkosi: Reduce kernel command line sizeDaan De Meyer2024-12-087-9/+19
| | | | | | | | | | | | The kernel command line has a size limit and we've hit it before so let's move some stuff to configuration files or scripts to reduce the kernel command line size a bit.
| * mkosi: Update to latestDaan De Meyer2024-12-081-1/+1
|/
* test: tentatively disable SELinux testsYu Watanabe2024-12-082-5/+4
| | | | | | | | Currently, mkosi GitHub action complains the following: === Could not find 'setfiles' which is required to relabel files. === Let's tentatively disable SELinux test.
* sysupdate: fix typo in DBus configAbderrahim Kitouni2024-12-071-1/+1
|
* test: Remove old bash test runnerDaan De Meyer2024-12-06132-5892/+0
| | | | | | We put a timeline of 257 to remove the old bash test runner so since we're about to release 257, let's remove the old bash test runner in favor of the meson + mkosi test runner.
* Revert "journalctl: show coredumps again when --unit= is specified"Zbigniew Jędrzejewski-Szmek2024-12-061-1/+3
| | | | This reverts commit cbd5f5d7d6d652d52a18170123f5d08baf7e9862.
* journalctl: show coredumps again when --unit= is specifiedYu Watanabe2024-12-061-3/+1
| | | | | | | | | | | | | | | | | | | | | This effectively reverts fdcd37df3b97abc381c7b7a29b81cc013c7a3230. After 888e378da2dbf4520e68a9d7e59712a3cd5a830f, coredumps for system services are stored by systemd-coredump user. Henve, _UID=0 does not match anything anymore. Before: ``` $ build/journalctl -u systemd-networkd.service -p2 -n1 -- No entries -- ``` After: ``` $ build/journalctl -u systemd-networkd.service -p2 -n1 Dec 06 05:39:55 H systemd-coredump[4187]: [🡕] Process 4145 (systemd-network) of user 192 dumped core. (snip) ```
* po: Translated using Weblate (Russian)Sergey A2024-12-061-4/+3
| | | | | | | | Currently translated at 100.0% (257 of 257 strings) Co-authored-by: Sergey A <Ser82-png@yandex.ru> Translate-URL: https://translate.fedoraproject.org/projects/systemd/main/ru/ Translation: systemd/main
* More assert macros (#35471)Luca Boccassi2024-12-065-1330/+1052
|\
| * test-parse-util: use ASSERT_* macrosZbigniew Jędrzejewski-Szmek2024-12-051-676/+596
| |
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-29 23:28:12 +0100