IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Fixes https://github.com/systemd/systemd/issues/32680#issuecomment-2120974685.
===
May 21 02:45:08 TEST-74-AUX-UTILS.sh[2475]: + mountpoint /tmp/tmp.eaRV7lSbX2/mnt
May 21 02:45:08 TEST-74-AUX-UTILS.sh[2476]: /tmp/tmp.eaRV7lSbX2/mnt is not a mountpoint
May 21 02:45:08 TEST-74-AUX-UTILS.sh[2449]: + systemd-mount /dev/loop0 /tmp/tmp.eaRV7lSbX2/mnt
May 21 02:45:08 systemd-mount[2477]: Failed to start transient mount unit: Unit tmp-tmp.eaRV7lSbX2-mnt.mount was already loaded or has a fragment file.
===
(cherry picked from commit 4a8ca3c6d595598f64cf532fad2c98ef7481f6a4)
Follow-up for ade0789fabbf01b95bf54d32f8cab1217a753f03
The change in behavior was partly intentional, as I think
if both --wait and --pty are used, manually disconnecting
from PTY forwarder should not result in systemd-run exiting
with "Finished with ..." log. But we should check for
--wait here.
Closes#32953
(cherry picked from commit 2b4a691c32aadbc45491c8b243ec3cf7ed910f55)
Coverity gets confused since the iterator change, so add an
assert to indicate that this is allocated if n_old_groups is > 0
CID#1545922
Follow-up for 125cca1b51e19d9209a229fca4fb9d94d34c3e78
(cherry picked from commit 5e30e6e28190fe30e76e071b2eb99546abcee7e6)
Otherwise, journal entries comes during sleep may not be read.
Follow-up for c22a112883a46e302dae587b809c459647363ceb.
(cherry picked from commit 123acb25605f904c9a52c67f00dfff2b299a7a58)
When running inside an LXC container the 'su' process will not be part of
any unit or slice.
manager_get_user_by_pid() which was used until v255 (included) does not fail
if it cannot find a unit/slice, but simply returns 'not found'. Do the same
in manager_get_session_by_pidref().
This was not detected as Semaphore CI does not reboot the testbed before
the logind test, so the session is started by the old logind from the base
distro, instead of the one being tested.
Follow-up for 8494f562c8963d8a936b0598e23eab277ff29374
Follow-up for 5099a50d4398e190387d204f5df81cc176bd33e2
Fixes https://github.com/systemd/systemd/issues/32929
(cherry picked from commit eb56b564a04b2c34a80bea9ede541c573fb41501)
Due to the bug in kernel 6.9 caused by
8debcf5832,
the net_id udev builtin does not work for netdevsim interface.
So, eni99np1 cannot be used with kernel 6.9 anymore.
Workaround for #32910.
(cherry picked from commit f1f1be71feacb3b5d2fb89e2f6421c23b9320fbd)
Fixes a bug introduced by 1ddb263d21099ae42195c2bc382bdf72a7f24f82.
Note, this requires the previous two commits, and cannot backport without them.
Note, before the previous commit, the use-after-free could be triggered
only by Rename() DBus method, and could not by RenameImage(), as we did not
cache Image object when RenameImage() method is called. And machinectl
always uses RenameImage(). Hence, the issue could be triggered only when
Rename() DBus method is explicitly called by e.g. busctl.
With the previous commit, the Image object passed to the function is
always cached. Hence, the issue could be triggered even with machinectl
command, and this fix is important.
(cherry picked from commit 3b1b2d4e3d544c593399e914fd1c3a5f61d7e827)
Previously, Image objects were only cached when reading properties or
methods in the org.freedesktop.machine1.Image interface are called.
This makes that, when a method in the main interface (org.freedesktop.machine1)
for an image is called, also acquire the Image object from the cache,
and if not cached, create Image object and put into the cache, like we
do for org.freedesktop.machine1.Image.
Otherwise, if some properties of an image are updated by methods in the main
interface, e.g. MarkImageReadOnly(), the changes do not applied to the cached
Image object, and subsequent read of proerties through the interface for the
image, e.g. ReadOnly property, may provide outdated values.
Follow-up for 1ddb263d21099ae42195c2bc382bdf72a7f24f82.
Fixes#32888.
(cherry picked from commit c6aeb9b596749b263145346c7fa2c6bf7fbd3867)
Same as the previous commit, but for SetLimit DBus method vs Limit
property and friends.
(cherry picked from commit 96ac6d3fccfe84eeda806da3d132a1374f8b5216)
Otherwise, ReadOnly DBus property in org.freedesktop.machine1.Image or
org.freedesktop.portable1.Image will not be updated by MarkReadOnly DBus
method.
(cherry picked from commit 608c321f232105966e509265c13ae061c03b9f77)
The rationale is similar to 40e1f4ea7458a0a80eaf1ef356e52bfe0835412e.
Currently, we only pass TTYPath=/dev/pts/... to
the transient service spawned by systemd-run.
This is a bit problematic though, when ExecStartPre=
or ExecStopPost= is used. Since when these control
processes get to run, the main process is not yet
started/has already exited, hence the slave suffers
from the same vhangup problem as the mentioned commit.
By passing the slave fd in, the service manager will
hold the fd open as long as the service is alive.
Fixes#32916
(cherry picked from commit 28459ba1f4df824d5ef7f7d1a9acb6953ea24045)
Follow-up for 6c2d47d6d3ad25ffd7527c7f4de31457ee1b25d8.
Fixes the following unexpected skip:
```
[ 6.163670] TEST-64-UDEV-STORAGE.sh[596]: + modinfo btrfs
[ 6.164102] TEST-64-UDEV-STORAGE.sh[726]: /usr/lib/systemd/tests/testdata/units/TEST-64-UDEV-STORAGE.sh: line 726: modinfo: command not found
[ 6.164683] TEST-64-UDEV-STORAGE.sh[727]: + echo 'This test requires the btrfs kernel module but it is not installed, skipping the test'
[ 6.165069] TEST-64-UDEV-STORAGE.sh[728]: + tee --append /skipped
[ 6.166801] TEST-64-UDEV-STORAGE.sh[728]: This test requires the btrfs kernel module but it is not installed, skipping the test
[ 6.167177] TEST-64-UDEV-STORAGE.sh[596]: + exit 77
```
(cherry picked from commit 2569e790f6352797f8e326ed472f49479791a2ac)
"norecovery" was deprecated for btrfs in
74ef00185e
and removed in
a1912f7121.
Let's drop our assumption that btrfs supports "norecovery" and first query for the
new name of the option followed by querying for the old name.
(cherry picked from commit e3828d7103a99a15a1e947ba3063294ead590631)
Otherwise, expected lines may not be processed or not sync()ed to disk.
Fixes#32712.
(cherry picked from commit c22a112883a46e302dae587b809c459647363ceb)
Previously, one of the test route has the same address in destination
and gateway. Even it is a test case, that's super spurious. Let's use a
different address.
(cherry picked from commit cd6507538a5bd233c94b46c3aba328abc216154c)
Avoid regressions like https://github.com/systemd/systemd/issues/32856
Follow-up for 2ef7cdc4255883d1c50860661248c9db69a86aa1
(cherry picked from commit 88e791171aaaa2484c0482a1e7c06ae8fd90e52a)
.osrel is also optional, but sd-boot and bootctl requires it.
So, let's keep .osrel section at least now.
Fixes#32774.
(cherry picked from commit 2e93331605e6b6a919121fd957a852431b0b8a19)
If tests are run during build time, without an already installed
systemd they fail to resolve the sysusersdir and tpmfilesdir pkg-config variables.
(cherry picked from commit 2aee829fc88fdde3983080de5c56fa06eb678280)
We want to eanble running tests as part of the build, but
our builds run in VMs with networking disabled.
(cherry picked from commit 19614a08d13fb8e0e73f1cb5859f8011e7df2394)
The test-event test seems to be taking quite a bit more time than
the other 'simple tests', which usually complete in < 1s. In case
of a slower or loaded machine the default 30s timeout is not enough.
(cherry picked from commit 381c3b64d0a80ccda2ccb0dda6fe825878a6e150)
If we destroy both an event loop and a curl contect object at the same
time, then we get into this weird situation where curl wants us to
reconfigure a timout event source right before destruction, which
sd-event will refuse however, since it is already being shutdown.
Hence, catch that and simply don't bother adjusting the timeout, since
we cannot get back from there anyway.
(cherry picked from commit c5ecf0949460dd0bf3211db128a385ce6375252e)
The state might be "freezing-by-parent" as well so let's take that
into account.
Fixes#32746
(cherry picked from commit 034e85c5f3608b8ae48ab1ad76b8af0b2c2fd3e5)
This should be useful when the test run as a service, e.g.
running on a mkosi image.
(cherry picked from commit e92d7b7dd9dd8d8783e44626268aa6315331d68c)
