| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
No functional change, just refactoring.
|
|
|
|
| |
No functional change, just refactoring.
|
|
|
|
| |
No functional change, just refactoring.
|
|\
| |
| | |
network: add mechanism to configure default UseDomains= setting
|
| |
| |
| |
| | |
page and add test
|
| |
| |
| |
| |
| | |
The diff looks bigger, but that's only because it seemed fitting to
reformat the paragraph now that the list is shorter.
|
|\ \
| | |
| | | |
tree-wide: trivial style and typo fixes
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Follow-up for e42a74803a5a9a8acf0d630dd775736610af4600.
|
| | |
| | |
| | |
| | | |
Follow-up for 21b366121f02aaeba5ba8c7597bba21c450172b5.
|
|/ /
| |
| |
| |
| | |
Fixes issue #32026 by only finding firmwares which explicitly support
the native architecture.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It shouldn't fail at that point.
It's prompted by the "Structure needs cleaning" thing that keeps popping
up in various places like
https://github.com/systemd/systemd/pull/30952#discussion_r1553181309 and
https://github.com/systemd/systemd/issues/31708.
|
|\ \
| | |
| | | |
shared/killall: minor modernization
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
sd-dhcp-server: use close_and_replace (avoid fd leak)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Follow-up for 11b88419ae0004547a0724aa459ddcb5d243f25c
Fixes #32252
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | | |
Fixes issue #32024, using --discard-disk=yes will enable handling of disk
discarding requests, saving space for long running VMs as desired.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This requires a Coverity license, so the usefulness of the instructions
is somewhat limited, but at least I won't have to re-discover everything
from scratch when I need to debug something Coverity-related again in the
future.
|
| | | |
|
| | |
| | |
| | |
| | | |
Follow-up for d04c1a1c8e7c95daa483d8d52d5fc4c25fbc67f2
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
systemd-255 is failing a build with the latest kernel headers… Let's downgrade
this warning, because it's fine if there's a file system we don't know about
and it makes thing less brittle if we don't treat this as a hard error.
(I initially conditionalized this on BUILD_MODE, but I don't think we need a
hard error there either. A warning will be noticed and fixed.)
|
| | |
| | |
| | |
| | | |
Fixes https://github.com/systemd/systemd/pull/32215#issuecomment-2049624693
|
|\ \ \
| | | |
| | | | |
network/ndisc: fixlets for on-link prefix
|
| | | |
| | | |
| | | |
| | | | |
Replaces 155d7a2c049cf866a0bfde8de371f09dfb3b6f29.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This effectively reverts commit 155d7a2c049cf866a0bfde8de371f09dfb3b6f29.
From RFC 4861 section 6.3.4:
> Note, however, that a Prefix Information option with the on-link flag
> set to zero conveys no information concerning on-link determination and
> MUST NOT be interpreted to mean that addresses covered by the prefix
> are off-link.
So, we should not drop previously configured routes when receieved a RA
with Prefix Information option without on-link flag.
Closes #28435.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Fixes issue #32025, I saw no reason not to enable this by default so I
added it to the initial qemu cmdline.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
yuwata/network-ndisc-redirect-fix-sender-address-verification
network/ndisc: fix sender address verification of Redirect message
|
| | | |
| | | |
| | | |
| | | | |
See RFC 4861 section 8.1.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The sender must be the first-hop router of the destination. Previously,
we only accepted Redirect messages whose sender is the current default
router with the highest priority.
See RFC 4861 section 8.1 for more details.
Fixes #31981.
|
| | | |
| | | |
| | | |
| | | | |
No functional change, preparation for later commits.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It is now called by only ndisc_redirect_handler(), and the check in
ndisc_request_redirect_route() is redundant and already done by
ndisc_redirect_verify_sender().
No functional change, just refactoring.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Hence, ndisc_router_update_redirect() does nothing. Let's remove it.
Also, ndisc_request_route() does not set lifetime for the route, it is
not necessary to set the third argument.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Then, make ndisc_request_route() generic and usable for configuring
routes based on both Router Advertisement and Redirect messages.
Note, ndisc_request_router() never set lifetime, so the dropped comment
in ndisc_request_redirect_route() is wrong.
No functional change, just refactoring.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Setting MTU announced in RA message to routes is problematic, as the
value may be larger than the device MTU (IFLA_MTU), and in such case the
route cannot be used.
These two properties are now set per-interface, and gracefully handled
such invalid cases. Hence not necessary to set them to each route.
Follow-up for #32195.
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
bpf_rdonly_cast() was introduced in libbpf commit 688879f together with
the definition of a bpf_core_cast macro. So use that one to avoid
defining a prototype for bpf_rdonly_cast;
|
| | | |
|
|\ \ \
| |/ /
|/| | |
A couple of follow-ups for #32189
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Unfortunately bfd30e8af6 is not enough and the test fails, that still
occasionally occur, don't provide enough information to see what's
wrong. Let's rework the test a little to improve this, namely:
- redirect curl's output into a temporary file instead of piping it
directly into the "check" expression; that way we can simply dump
the temporary file when the test fails, providing potentially
crucial information. We don't want to always dump everything to
stdout, as some of the tests request an entire system journal (note
that shell redirection instead of `curl -o file` is used
intentionally, so the output file is always nuked first)
- by dropping the pipes in curl commands we can re-enable pipefail
- also, split some very long commands to multiple lines to (slightly)
improve readability
Follow-up for bfd30e8af64a0d39ad110258dca69be919f6df34.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The logs from TEST-69 still contain a lot of unnecessary shell
metacharacters, so to make the output more readable let's just set
TERM=dumb, instead of having to strip everything semi-manually. Also,
move the related --background= tweak to TEST-69, since it's relevant
only for that particular test.
Follow-up for 8d4bfd38ed941aa8003d7007145eccc01f52a5f6.
|
|\ \ \
| | | |
| | | | |
network/ndisc: fix assignment of valid lifetime
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This makes the logic mostly follows RFC 4862 section 5.5.3 (e),
as draft-ietf-6man-slaac-renum-07 is deprecated.
Fixes #31449.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Follow-up for 43d184682d640e438ad140b0743e2fd258455b12.
No functional change, just refactoring.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
pcrlock writes a credential file using null key. Make sure systemd-creds
can show the file
|
|\ \ \ \
| | | | |
| | | | | |
journal-remote: Use sd_event_set_signal_exit()
|