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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Follow-up for efedb6b0f3cff37950112fd37cb750c16d599bc7.
Closes#35116.
(cherry picked from commit 985ea98e7f90c92fcc0b8441fafb190353d2feb8)
Really rewritten from scratch.
(cherry picked from commit 04ee5e25a1082d4c6c0c52a154d5ad5fc959a853)
(cherry picked from commit 45b39f98c9abfcf305641d697392aacbf5e022d0)
(cherry picked from commit c25b73f93b369861259244e5a8c55cf82d97adb8)
(cherry picked from commit 2a774f064815573efc33d43dfe3548590e42e9c2)
(cherry picked from commit 56cc8acf45dbff227d1713d509bc3b71386df5d8)
(cherry picked from commit 2e956d084024b7cc984528719e866b3d9f2f59eb)
(cherry picked from commit d3132ec4944279f1c8f4968888710ba821083e56)
(cherry picked from commit 9eee6b1b3f00d46459eebefb70be50ea6af30ddb)
(cherry picked from commit f3baba94425e6ccaf7a672903148dbb2b9e022f7)
(cherry picked from commit be571ff64808c30c1d5566600c86084768138bc4)
(cherry picked from commit ca169c9e8be3ade4627acdb9460663a755cb9a64)
Outside of x86, some machines (e.g. Apple silicon, AMD Opteron A1100) have
physical memory mapped above 4GiB, meaning this allocation will fail, causing
the entire boot process to fail on these machines.
This commit makes it so that the below-4GB address space allocation requirement
is only set on x86 platforms, and not on other platforms (that don't have the
specific Linux x86 boot protocol), thereby fixing boot on those that have no
memory mapped below 4GiB in their address space.
Tested on an Apple silicon M1 laptop and an AMD x86_64 desktop tower.
Fixes: #35026
Manual backport of 6e207b370e91e681efb08c497a6c8ad78e3c8d83.
(cherry picked from commit a9d9db7f4e4a75f6dbda5c31fbbf325eff9d63b4)
(cherry picked from commit 8923d937684dba17a84dc3693e77adeb4a4f4ec8)
(cherry picked from commit 6f0a01d3c01da0dae1eb744429b77b3d310a24ff)
The concept of synthetic errnos is about logging, which
is irrelevant irt bus error and we don't do any special
treatment in sd-bus for them, meaning the value propagated
would be spurious.
(cherry picked from commit 2f2058da0b88535cb3a95fc98e7b2f1ae4d35601)
(cherry picked from commit 018c7fb18ae8aff5414d5e74cb41fb98b72c0554)
(cherry picked from commit 39c2b7fd58d4b96fc4f5fe0d5ebbfcc3cf1c3f80)
(cherry picked from commit 06be1bfc838edc803096321e403021c005404283)
It seems there is no restriction for local and remote addresses.
Fixes#34930.
(cherry picked from commit 5e48fd0506ed6212c9db2276d5845ab77aa9bce4)
(cherry picked from commit 3093ac05abcaf5a43f75ec1d5702ed226cc3ce31)
(cherry picked from commit 81c84336f47e1bcfa3b63ae4eb3889e249537e64)
(cherry picked from commit 6f19e9fa9cb6350fd69685b44878cc94357f9ad1)
`loginctl kill-session --kill-whom=leader <N>` (or the D-Bus equivalent)
doesn't work because logind ends up calling `KillUnit(..., "main", ...)`
on a scope unit and these don't have a `MainPID` property. Here, I just
make it send a signal to the `Leader` directly.
(cherry picked from commit 8254755091847105c33e473c62cdc7621ed275bc)
(cherry picked from commit c89c5d04f33dbc5c6dfb67b8bc58cbd3d924b434)
(cherry picked from commit 80efb1da3f073daec9f84dd83571a7b98451f953)
(cherry picked from commit 94b234df968b9ebfd7fd57f45982f3fee6a61f9d)
To keep align with the logic used in udev_rules_parse_file(), we also
should skip the empty udev rules file while collecting the stats during
manager reload. Otherwise all udev rules files will be parsed again whenever
reloading udev manager with an empty udev rules file. It's time consuming
and the following uevents will fail with timeout.
(cherry picked from commit 2ae79a31b7c7947e2c16e18eb85ac5607ebc40b6)
(cherry picked from commit 688eb20fdb9c4bcc6d205323f9cec119d6273169)
(cherry picked from commit 484d31a58d7b820fa83a70a9f654b907130eec75)
(cherry picked from commit 8b6ae951d389cf9e2caccd752afdd32dcdca2ed3)
Processes can easily survive the first kill operation we execute, hence
we shouldn't make strong claims about them having exited already. Let's
just say "likely" hence.
Fixes: #15032
(cherry picked from commit ac804bc2f8d814d2afcdccd88f7469ac320da1c8)
(cherry picked from commit 307a6332a63dd0f6addbc5c77d21f72ce4578070)
(cherry picked from commit b38386ae2bff5cc55a83094a625a026e23a69e0c)
(cherry picked from commit e23cbecd7fbec8a99c7fc466d49c69724fcdee68)
In https://bugzilla.redhat.com/show_bug.cgi?id=2322937 we're getting
an error message:
Okt 29 22:21:03 fedora systemd-resolved[29311]: Could not create manager: Cannot allocate memory
I expect that this actually comes from dnstls_manager_init(), the
openssl version. But without real logs it's hard to know for sure.
Use EIO instead of ENOMEM, because the problem is unlikely to be actually
related to memory.
(cherry picked from commit ee95e86ae163e436384f1b782a77a7e18deba890)
(cherry picked from commit abd1e408203d5d445b05f4dc0ac07e35114532d1)
(cherry picked from commit 67954b455473b29f8a41be14f5b778044b7cfafa)
(cherry picked from commit 17a3a8e91be80c93347458a1a6508bc19646607d)
log_info appears to be the preferred method to convey information from
tests. Convert all the printfs to log_info to follow this standard.
(cherry picked from commit 38557d9ffbc6351b8980faf90d54619790436d43)
(cherry picked from commit 4ea84288480115f7175a8cfc61d03e3a712396b8)
(cherry picked from commit cfa083d450b2cd21676651d9489fbcf4dfd1b9f1)
(cherry picked from commit 6dda2e10a0b289089c2a65b09821ab9541b70a59)
Users will generally know what a qrcode is, so let's not treat them as dumb and
explain that it can be scanned. OTOH, we should say what the qrcode contains
and it is useful to give a hint why the users would want to scan it. Reword
messages accordingly.
(Also, don't say "to your phone", when somebody might be using a stolen phone,
or something else then a phone.)
(cherry picked from commit 10faa40ba781cf499258a3b37de02dd643822dc6)
(cherry picked from commit fefd60bf7ad9f361c85395ab38f10482f3007f15)
(cherry picked from commit 4ca8f5e68dc86606890806d7c17ae71d17e1cd9a)
(cherry picked from commit d415c1d8a321d13012081a7f31533db064311b1a)
This makes it easier to diagnose why colors are disabled.
(cherry picked from commit b137b2979868e2de5fb5c26e90bacee33597b8e7)
(cherry picked from commit bbdb5f97a96e5942bb055770366e0d48c3ee8540)
(cherry picked from commit f120804bb746113d911e8bdf53616aa21a6ecf6b)
(cherry picked from commit f40708b6de482aa2fdd785d6047c22694ebc6414)
We would need to use pure if the funtion was getting pointers and
dereferencing them. But sd128_t is a structure and those functions
only access the parameters of the call.
(cherry picked from commit dc32b09b70c9bb20821df92ac82ace83d8a968e2)
(cherry picked from commit 3190a427b915976c9c11979acad20682e947a3c8)
(cherry picked from commit b166ddd3dccce64c76040e098621ba7627f987c6)
(cherry picked from commit e0aa86901231315aacd080dc79027e64da457455)
(cherry picked from commit 1e8f0beee4272ddc8b25dfa9af8e54bafc4c061a)
(cherry picked from commit b9ff85ece7a6bd9eca158aa0a8af46055ffb6142)
(cherry picked from commit e575661da99de81bf0f07d7efdcf8b4c5d9b779e)
(cherry picked from commit 12b7b9e50cc19081c328e31937f7ddd764e16b41)
Fixes a bug introduced by baf3fdec27f0b3a1f3d39c7def2a778824cbee51.
This also adds several assertions at the beginning of the function.
Fixes#34899.
(cherry picked from commit 5dc0668802cd07cdca2dc5bda52cc1e63b57f145)
(cherry picked from commit 7455e7622113969866ed116d101aa54cfe2b1f7e)
(cherry picked from commit 261469e369c0d2ea6dafb27b745d771ab98f627b)
(cherry picked from commit e5f6d457d4b4b337eddd02120b12cbaa60cdfb59)
virtio console uses /dev/hvc* so we need access to write wall
messages
(cherry picked from commit 5ff6841c2378ed83e645681cbd4ee145f68d72b7)
(cherry picked from commit 0852240f927f47100b61e3b33e34a0f74b0d6a90)
(cherry picked from commit ccb963233d9dc6db693b2206cd37bb9e3247e5ee)
(cherry picked from commit 9e47ce3ab7abeb1edf854110f2ec83be2a78ab56)
The links moved to the legacy dataset so they won't be available by
default, so stop using them and just use the city ones instead
(cherry picked from commit aa077884c13769ae3bd6aa98978b4ac9e64b5365)
(cherry picked from commit 4a3fc628a24b5f13af350691ff50f8be905c9c9c)
(cherry picked from commit 484cd8584cb208bd44a54e24302dca31a1139608)
(cherry picked from commit c2d3456d89fface7bbc5a86c205bdb14c990bf80)
(cherry picked from commit 9b1a5bc365e379b4b13849adacfde3427f55ca38)
(cherry picked from commit a816075978767187f1a172326f414f67d905001b)
(cherry picked from commit e6247b048f4a37af0f79088e921262232236e339)
(cherry picked from commit 207ee49f20545004456bff1c7a3934a69b0b11ee)
This might have the effect that some DNS server or search domain
disappears, hence rewrite the relevant files.
See: #27543
(cherry picked from commit 562f7bde8872b4fd03db11bf25c9dd294fd2c186)
(cherry picked from commit 72806073770393982a50aed54c40164105c9bf14)
(cherry picked from commit 1de3aa4ec90cfa3f6568426982207141a1feabf0)
(cherry picked from commit cea9e1619a0b150b08d5481f01546b7a898aad01)
Limits should be enforced, but not in a way real setups collide with
them.
There have been multiple reports that current limits are too low, hence
raise them 8x.
Fixes: #24852
(cherry picked from commit af7674f4ad30e83efc84f04c45f01e6eff137702)
(cherry picked from commit dc47ba69fcc6ff01b813777b126f4cf9b571a9c9)
(cherry picked from commit c0d234ac2ed0cb14f237f8aa4ea61abc5bdb4a11)
(cherry picked from commit 15c33cb70902c868f7779ea69a5c06d822454fdb)
Various archs do not know the "io port" concept, hence check for the
"iomem" configuration, too.
Fixes: #34800
(cherry picked from commit 9da582984b632a75f562a304ff96dd1043281430)
(cherry picked from commit 7803507b6e2a0e120e73b6a66460e458d72b0207)
(cherry picked from commit fadf1b15361cb0627c61df0e3fa304b9b833bfc6)
(cherry picked from commit 749df25830edaaff0c662d80c662b5ef0467e2b9)
(cherry picked from commit c5928a768417b298eb2741107fa7492e93d637fc)
(cherry picked from commit 3b171cb7bc6d84381f8ac27722503b103745cd2b)
(cherry picked from commit ee80f6b05ce022a2803f9bcd31c81b28bbb5992b)
(cherry picked from commit 7a64921bc27f054c169d743ef0aa22d669e4e45d)
../src/resolve/resolved-bus.c: In function ‘call_link_method’:
../src/resolve/resolved-bus.c:1769:16: warning: ‘l’ may be used uninitialized [-Wmaybe-uninitialized]
1769 | return handler(message, l, error);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
../src/resolve/resolved-bus.c:1755:15: note: ‘l’ was declared here
1755 | Link *l;
| ^
../src/resolve/resolved-bus.c: In function ‘bus_method_get_link’:
../src/resolve/resolved-bus.c:1828:13: warning: ‘l’ may be used uninitialized [-Wmaybe-uninitialized]
1828 | p = link_bus_path(l);
| ^~~~~~~~~~~~~~~~
../src/resolve/resolved-bus.c:1816:15: note: ‘l’ was declared here
1816 | Link *l;
| ^
(cherry picked from commit 5f911aca8434b4163514019fcb4c1c967a50617c)
(cherry picked from commit 2590b77f39f7c1264b686e0b379465f5670631d3)
(cherry picked from commit 4c9509ad0c57a88370be9e938e3e130a3398e4c5)
(cherry picked from commit 7d275f119c21bb2db8b35b34743898f4c908c7fa)
Even optarg is erased, copied string was not erased.
Let's erase the copied key for safety.
(cherry picked from commit d0ad4e88d4e6b5e312c359a6505125f7e088f3e3)
(cherry picked from commit 28f7c958fb799887cb67528a85ca59f0ccd9261e)
(cherry picked from commit 6b13398c220a01e2eff5bb25da7d457f445c82e9)
(cherry picked from commit b115781317b6a8c649ae2b92c7839ce8872fdffb)
(cherry picked from commit 5f3cfb9d5ee334c53cc407308ba677401a6ba1cd)
(cherry picked from commit 04bf8544baa3ef4c675e610f35dd44f2ea60382e)
(cherry picked from commit 41ebd133657cbf83b202fe132ea96c0ae2906fc8)
(cherry picked from commit 481f29f7fa7cf44548da063c74a3c2c5f6088658)
Fixes a regression caused by 84ebe6f01381c21b88e37e856956c9c9ee6781d6 (v250).
Fixes#34773.
(cherry picked from commit 77bbd9f1bd2b01bcb2a49ed42c6dc06613532bcf)
(cherry picked from commit a94b2c39f94e7af82a56c52941cc1c6aeaf2318f)
(cherry picked from commit 71fca73f70c96fb9c7573d73d6eae2c5fccd1d56)
(cherry picked from commit 556f0549d317e2ea4342fc684d89ce354e42d66d)
Follow-up for f963f8953daeab03b892616ce0c65f7572932187 and
1536b7b2d00819615bf8eba194de7ccd20c3689f.
(cherry picked from commit 8fead9c9e46e5f71ae6f6b038ff7f72c5a13b663)
(cherry picked from commit 30cf66855b6e31e7de2bff6d79d5c2d9fc17d684)
(cherry picked from commit f4189fdd1de998703feb9ca221b700fdaee5cd31)
(cherry picked from commit 51ed671255ed2313e17869e01b9bb7fa587a1ea1)
This adds the missing colon character to the section systemd-sysusers.
(cherry picked from commit 8ef5ea2bf6d8c9ef12b00ab3838b9af81e30bf5d)
(cherry picked from commit 6a288cd999090661461be74f24fd29cb90da1f3f)
(cherry picked from commit a2c6d50b6480e150e8df110178e98d1888395067)
(cherry picked from commit 4b21746e2110cd1875f9a7278a7aa2ce36ab3519)
(cherry picked from commit c9b477415a6293b74df67c8118bafb0ef8662819)
(cherry picked from commit 1f0d68c6e9dc7cc9bd14f47d03eec10389e2c845)
(cherry picked from commit 833a89efc70c56fd7a143369efaf33212bb06021)
(cherry picked from commit 6bb1aba7533bab897107811ef1d789cacdfc0c91)
(cherry picked from commit 8b8668b9e71837cb541cd432bc37e4c9405e49cd)
(cherry picked from commit c7762098ec09c2626204c9580c91295414137bba)
(cherry picked from commit b095673440f3c0ab434475cf539aff018e7f5e20)
(cherry picked from commit d1bc81ba33996c8881ec0716c1ea22bde329bbc8)
This is a new syscall provided by the kernel used to implement faster
uprobes. It's not supposed to be called by userspace, but only by kernel
generated uprobe code.
It should be fine to allow this, as the kernel authenticates the
invocation itself, and we shouldn't break compat with things.
Note that this allowlisting is not sufficient to make ureprobe() work.
libseccomp must be tought the syscall too, but this can happen
independently.
Fixes: #34615
(cherry picked from commit d693c483a2bb3eae490fd78d68fc16d0a731fee2)
(cherry picked from commit 389fbf464907132479cd1d18c7cbee17328f36cf)
(cherry picked from commit 1fd57ca01c180fd77b626e0f091762ecd1e2736c)
(cherry picked from commit bde6caa9efbffd0e1b8220231a22bdb59c9b78f4)
(cherry picked from commit 882032faaf9e2d2524936e82ccc770903d4c38d6)
(cherry picked from commit c14a47547d040c4976f20388f5535ed655bbd035)
(cherry picked from commit 40ea469735cb869c98c9bd3e651a25b74cade631)
(cherry picked from commit 9d7f1c6bc1579bb067b6077e4488024e97cc989b)
The documentation claimed that ExecStartPre=/ExecStartPost= accepts
multiple command lines, in contrast to ExecStart=. This is half an
untruth, because ExecStart= allows that too – as long as Type=oneshot is
set.
Hence, reword this a bit, and do not emphasize the contrast.
Prompted by: #34570
(cherry picked from commit c3069a6bfb454a0e02607ad21b5badf9847fe11a)
(cherry picked from commit ff667d8c2ef7ed2378fb1de39e1bcc2af2197d0e)
(cherry picked from commit d0063ca6949c2b3dfad3e233f5ac10df928d6b12)
(cherry picked from commit 4e2337232959e431217b860f2a27599d74e9eb40)
In mount_load_proc_self_mountinfo(), device_found_node() is synchronously called
during the traversal of mountinfo entries. When there are a large number of
mount points, and the device types are not significantly different, this results
in excessive time consumption during device discovery, causing a performance
bottleneck. This issue is particularly prominent on servers with a large number
of cores in IDC.
This patch decouples device discovery from the mountinfo traversal process,
avoiding redundant device operations. As a result, it significantly improves
performance, especially in environments with numerous mount points.
Signed-off-by: Chen Guanqiao <chen.chenchacha@foxmail.com>
(cherry picked from commit 00ad3f02275b507a753495ace5e5f84cb38b604d)
(cherry picked from commit 44e1774660fcddcfefcf153cc3c189ea35572d63)
(cherry picked from commit ea35f88ae763b4f99d57c4ec7fd0d3aa6351a352)
(cherry picked from commit 7ed40368310297c2321be0aaf08526b3d390c75b)
(cherry picked from commit a41da1e7037dc36a601d3428343bbc7f0eed3e20)
(cherry picked from commit 697d247e308828e74132305606f73078616f42e2)
(cherry picked from commit 54a43fe71072f649beafe839dfd44b58b348740e)
(cherry picked from commit 4e089fc7ad5eb942a423bba3485167c81d8ce24d)
(cherry picked from commit f4e3c6e5b318d22a9c40144c6d52ae68a70c264c)
(cherry picked from commit 5a2f94d2dae50fbaa430a96a3096368dfc488380)
(cherry picked from commit 109da92157425ffecd4ef063b74439f611fdb305)
(cherry picked from commit 10808d1efba40252e56d06166554a07f5033a5ab)
We should not invalidate the socket address size before we use it.
Fixes: #34579
(cherry picked from commit 5699e4c2d470a12c922c4b7c86a8987837911626)
(cherry picked from commit 964f7772ad0ff637db80ae0a9e0afb41a40f5b04)
(cherry picked from commit 4dca5688cb4c97f9072fe1c668923b2e56bfdf15)
(cherry picked from commit 969f4f3ea1163a5caa2b22ca05ea68aaed97034b)
A daemon-reload is important enough to deserve logging at notice
level.
(cherry picked from commit 4ee41be82507348fbbc9d3ab28aae6330eb51663)
(cherry picked from commit 31e38b55b2e4bb1aa42fe106ea14df8e82758303)
(cherry picked from commit 79dc77a7ffed671a16c44369df2552cf733dbbef)
(cherry picked from commit 50e3bc139fc750c7b15bda55807fcb9209787319)
On jammy it started to fail, it's not really needed and we install
an empty stub anyway, so just mask the generator
(cherry picked from commit 565916c245b53b49f5917f5326d21246f46ae3db)
(cherry picked from commit dfb007ffe0a9aa3a1d0f7930131b129fbaa2b3d9)
This feature has been deprecated since QEMU 5.0 and finally removed in
QEMU 9.1 [0] which now causes issues when running the storage tests on
latest Arch:
------ testcase_long_sysfs_path: BEGIN ------
...
qemu-system-x86_64: -device virtio-blk-pci,drive=drive0,scsi=off,bus=pci_bridge25: Property 'virtio-blk-pci.scsi' not found
E: qemu failed with exit code 1
[0] a271b8d7b2
(cherry picked from commit cd57920fbf6a8f7769a82cfc9bebc12965de0199)
(cherry picked from commit c5baa5d9d9d778aee25b751387c60f43a0a6fb74)
(cherry picked from commit 192a6e99a950c9cbcbe2a79f9045a06a10ca0288)
(cherry picked from commit 1d2451056bc6bb0cfeb9b29504584216967780c5)
There are other CI runs that build manpages, speed up build which is close to 1hr limit
(cherry picked from commit d58a904d35d3abcb7265b28b14aac596631e27d6)
(cherry picked from commit 966d8a90ca44659123c15e3a7e7d498aa2b50510)
(cherry picked from commit 0c6e525a1f998c37849c04a215e5a68312331272)
(cherry picked from commit ece14d98c2ee8407b319a51405b598e0b0fda054)
This slows down the build, which is often near the 1hr limit. There are
other jobs running the extra unit tests.
(cherry picked from commit 3bc5480bac474263881e4c5919d5cce0debf3c40)
(cherry picked from commit 52afaa8034f59dda44ec181e79604a9a222e60ad)
(cherry picked from commit 3891c50ce67bb4aeda13e099240c684c6dd9ca25)
(cherry picked from commit 0c82cc26af64516f667eb34072dbf9ead3821798)
Builds have been failing as we run out of space in /tmp/, move to
/var/tmp
(cherry picked from commit 0c7b5dad33ee01b7ff6b7a8c583a7e2c27ac0673)
(cherry picked from commit bc0102b0caacb97041ada0b0dbca40da09eab453)
(cherry picked from commit 82baa27f9d1c5f15906b4aa9b9a40b3d900bec09)
(cherry picked from commit f19a717e989b7e37ccc6d8f51395d9ac856b0158)
