summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #19590 from keszybz/comments-and-service-modernizationYu Watanabe2021-05-136-35/+26
|\ | | | | Comments and service modernization
| * core/service: modernizationZbigniew Jędrzejewski-Szmek2021-05-121-12/+9
| |
| * test-bpf-foreign-programs: fix messageZbigniew Jędrzejewski-Szmek2021-05-121-1/+1
| |
| * sd-event: tweak commentsZbigniew Jędrzejewski-Szmek2021-05-121-4/+3
| |
| * timedated: make ntp_synced() staticZbigniew Jędrzejewski-Szmek2021-05-123-18/+13
| | | | | | | | No need to have this in basic.
* | Merge pull request #19567 from poettering/ipv4-ipv6-lowercaseZbigniew Jędrzejewski-Szmek2021-05-129-35/+48
|\ \ | | | | | | various follow-ups to socket-bind logic
| * | cgroup: drop explicit NULL comparisonsLennart Poettering2021-05-111-1/+1
| | |
| * | tree-wide: move variables to innermost scopeLennart Poettering2021-05-111-3/+1
| | |
| * | tree-wide: use af_to_ipv4_ipv6() + af_from_ipv4_ipv6() helpers at various placesLennart Poettering2021-05-116-27/+27
| | |
| * | af-list: add helpers mapping AF_INET/AF_INET6 to "ipv4"/"ipv6"Lennart Poettering2021-05-112-0/+15
| | |
| * | socket-bind: use lowercase "ipv4"/"ipv6" spellingLennart Poettering2021-05-115-14/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In most of our codebase when we referenced "ipv4" and "ipv6" on the right-hand-side of an assignment, we lowercases it (on the left-hand-side we used CamelCase, and thus "IPv4" and "IPv6"). In particular all across the networkd codebase the various "per-protocol booleans" use the lower-case spelling. Hence, let's use lower-case for SocketBindAllow=/SocketBindDeny= too, just make sure things feel like they belong together better. (This work is not included in any released version, hence let's fix this now, before any fixes in this area would be API breakage) Follow-up for #17655
* | | resolved.conf.in: add missing Quad9 serversMichael Catanzaro2021-05-121-1/+1
| | | | | | | | | The example configuration is missing half of Quad9's addresses.
* | | resolved: be more careful with weird links with low MTUsLennart Poettering2021-05-121-4/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Apparently CAN links will show up in rtnetlink with very low MTUs. We shouldn't consider them relevant if no IP is spoken over them, since these MTUs are irrelevant for us then. Hence, let's check if there's an address assigned to the link before considering its MTU. As additional safety net filter out MTUs smaller than the minimum DNS packet size, too. Finally, in case we don't find any suitable interface MTU, let's default to 1500 as the generic Ethernet MTU. Fixes: #19396
* | | Merge pull request #19533 from yuwata/network-queueZbigniew Jędrzejewski-Szmek2021-05-1229-1150/+2118
|\ \ \ | |_|/ |/| | network: introduce queue to configure address, route, etc
| * | network: make route_configure() return all created routesYu Watanabe2021-05-121-12/+38
| | |
| * | network: make log_route_debug() show multipath routes and Gateway=_dhcp4 or ↵Yu Watanabe2021-05-121-6/+27
| | | | | | | | | | | | _ipv6ra
| * | network: use request queue to configure addresses, routes, and nexthopsYu Watanabe2021-05-1216-572/+896
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Why is this necessary? Several examples below. - When a route sets prefsrc, then the address must be already assigned (see issue #19285), and also it must be ready if IPv6. - When a route or nexthop sets gateway, then the address must be reachable. - When a route sets nexthop ID, then the corresponding nexthop must be assigned. - When a route sets multipath routes on another interface, then the interface must exist and be ready to configure. - When configuring address, the same address must not be under removing (see issue #18108). Etc,. etc,... So, this makes all requests about addresses, routes, and nethops are once stored in the queue, and will be processed when they are ready to configure. Fixes #18108 and #19285.
| * | network: use request queue to configure neighborsYu Watanabe2021-05-126-36/+94
| | |
| * | network: use request queue to configure routing policy rulesYu Watanabe2021-05-128-63/+144
| | |
| * | network: introduce link_is_ready_to_configure() helper functionYu Watanabe2021-05-122-0/+21
| | | | | | | | | | | | This will be used in later commits.
| * | network: add skeleton of request queueYu Watanabe2021-05-126-2/+192
| | | | | | | | | | | | This will be used in later commits.
| * | network: nexthop: add NextHop object before sending netlink requestYu Watanabe2021-05-121-6/+6
| | | | | | | | | | | | | | | Otherwise, if nexthop_add() fails, then assertion about nexthop_messages in static_nexthop_handler() will be triggered.
| * | network: split out common part of route or address handlersYu Watanabe2021-05-128-171/+155
| | |
| * | network: change order of dropping network configsYu Watanabe2021-05-121-8/+8
| | | | | | | | | | | | | | | As routes may requires nexthops and addresses, nexthops may requires addresses.
| * | network: simplify and rename routing_policy_rule_copy()Yu Watanabe2021-05-121-38/+20
| | |
| * | network: introduce route_dup()Yu Watanabe2021-05-122-0/+39
| | | | | | | | | | | | The function will be used in later commits.
| * | sd-netlink: introduce multipath_route_dup()Yu Watanabe2021-05-122-0/+31
| | | | | | | | | | | | The function will be used in later commits.
| * | network: introduce manager_address_is_reachable()Yu Watanabe2021-05-122-0/+41
| | | | | | | | | | | | The function will be used in later commits.
| * | network: introduce link_has_route()Yu Watanabe2021-05-122-5/+68
| | | | | | | | | | | | The function will be used in later commits.
| * | network: delay resolving interface specifier in MultiPathRoute=Yu Watanabe2021-05-123-29/+53
| | | | | | | | | | | | The interface may not exist when .network files are loaded.
| * | network: introduce manager_has_address()Yu Watanabe2021-05-122-0/+58
| | | | | | | | | | | | The function will be used in later commits.
| * | ordered-set: introduce ordered_set_clear/free_with_destructor()Yu Watanabe2021-05-121-0/+11
| | |
| * | hashmap,set: make hashmap_clear_with_destructor() or friends saferYu Watanabe2021-05-122-23/+20
| | |
| * | network: use IPV4_ADDRESS_FMT_STR/VAL macros and in6_addr_to_string() or friendsYu Watanabe2021-05-125-128/+121
| | |
| * | in-addr-util: move IPV4_ADDRESS_FMT_STR/VAL macros from networkd-address.hYu Watanabe2021-05-122-7/+7
| | |
| * | in-addr-util: introduce in6_addr_to_string() or friendsYu Watanabe2021-05-121-0/+6
| | |
| * | network: use in6_addr_is_link_local() or friendsYu Watanabe2021-05-121-4/+4
| | |
| * | network: rename routing_policy_rule_configure_internal() and make it take ↵Yu Watanabe2021-05-121-55/+62
| | | | | | | | | | | | callback
| * | network: make nexthop_configure() take callbackYu Watanabe2021-05-121-33/+39
| | |
| * | network: make neighbor_configure() take callbackYu Watanabe2021-05-121-30/+35
| |/
* | Merge pull request #18986 from poettering/oomd-varlink-fixZbigniew Jędrzejewski-Szmek2021-05-122-26/+11
|\ \ | | | | | | varlink ref fix
| * | core: don't accidentally unref a varlink connection twiceLennart Poettering2021-05-111-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let's make sure that our close handler unrefs a connection again that we are already unreffing a few stack frames up by invalidating the pointer first, and dropping the ref counter only after that. Replaces: 39ad3f1c092b5dffcbb4b1d12eb9ca407f010a3c Fixes: #18025
| * | Revert "varlink: avoid using dangling ref in varlink_close_unref()"Lennart Poettering2021-05-111-24/+6
| |/ | | | | | | This reverts commit 39ad3f1c092b5dffcbb4b1d12eb9ca407f010a3c.
* | Merge pull request #19506 from xnox/ship-stub-elfZbigniew Jędrzejewski-Szmek2021-05-121-19/+22
|\ \ | | | | | | boot/efi: install ELF linux.elf.stub in addition to PE linux.efi.stub
| * | meson: rework test-efi-disk.img creation to not require variablesZbigniew Jędrzejewski-Szmek2021-05-101-21/+20
| | | | | | | | | | | | | | | The primary goal is to make the name of the custom_target() rule match the output file again. Having them different is confusing.
| * | boot/efi: add --build-id=sha1 to ELF efi objectsDimitri John Ledkov2021-05-101-0/+1
| | | | | | | | | | | | As it is not nice to ship ELF binary without a note.gnu.build-id set.
| * | boot/efi: install ELF linux.elf.stub in addition to PE linux.efi.stubDimitri John Ledkov2021-05-101-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | Binutils for non-x86 architectures currently does not support PE binaries. Thus linux.efi.stub is useless on those, as one cannot use any tooling to add linux/cmdline/splash sections to it. In addition to PE linux.efi.stub also install ELF linux.elf.stub, such that one can use objcopy ELF target to copy in linux/cmdline/splash sections and then convert the result to a PE binary.
* | | Merge pull request #19581 from yuwata/specifier-refuse-too-long-resultsLennart Poettering2021-05-1222-135/+169
|\ \ \ | | | | | | | | specifier: refuse too long results
| * | | tree-wide: refuse too long strings earlier in specifier_printf()Yu Watanabe2021-05-1215-88/+113
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We usually call specifier_printf() and then check the validity of the result. In many cases, validity checkers, e.g. path_is_valid(), refuse too long strings. This makes specifier_printf() refuse such long results earlier. Moreover, unit_full_string() and description field in sysuser now refuse results longer than LONG_LINE_MAX. config_parse() already refuses the line longer than LONG_LINE_MAX. Hence, it should be ok to set the same value as the maximum length of the resolved string.
| * | | dns-domain: use DNS_LABEL_MAX at one more placeYu Watanabe2021-05-121-1/+1
| | | |
View Lorry Controller Status