summaryrefslogtreecommitdiffstats
path: root/units/systemd-udevd.service.in (unfollow)
Commit message (Collapse)AuthorFilesLines
2020-07-16tree-wide: use SYNTHETIC_ERRNO with log_device_* in more placesZbigniew Jędrzejewski-Szmek4-28/+23
2020-07-16sd-device: use LOG_PRI() in log_device_full()Zbigniew Jędrzejewski-Szmek1-1/+1
We use LOG_PRI() in all log_*() functions, so let's do that here too for consistency. Effectively this doesn't change anything since we only use LOG_{INFO,DEBUG,...} as the argument.
2020-07-16analyze: CAP_RAWIO -> CAP_SYS_RAWIOAnita Zhang1-1/+1
Fixes #16489
2020-07-16udev: don't complain when udev_watch_end() is called without udev_watch_init()Zbigniew Jędrzejewski-Szmek1-2/+1
E.g. udevadm test prints "Invalid inotify descriptor." which is meaningless without any context. I think it should be OK to call udev_watch_end() from a cleanup path without any warning (even at debug level).
2020-07-16basic/string-table: reduce variable scopeZbigniew Jędrzejewski-Szmek1-3/+1
2020-07-16udevadm: use STR_IN_SET(), add commentZbigniew Jędrzejewski-Szmek1-11/+9
2020-07-16sd-device: use strjoin instead of asprintfZbigniew Jędrzejewski-Szmek2-36/+27
strjoin should be faster for string concatenation. Also drop "_"-prefix from function prototypes.
2020-07-16udev: tweak debug logs for udev rulesZbigniew Jędrzejewski-Szmek1-7/+7
We shouldn't say "ignoring" when running a program because the result is used for the match/nomatch result of the rule.
2020-07-16man: add more details for IMPORT, PROGRAM and RUN keysZbigniew Jędrzejewski-Szmek1-32/+47
967de8faceaa83c11a1215515cb135d7a8c0c32c added a note that I found very hard to understand. Reword it, and also describe how IMPORT and PROGRAM are different from RUN. Minor markup adjustements too.
2020-07-16udev: accept OPTIONS+= without any fussZbigniew Jędrzejewski-Szmek1-3/+1
There is no reason to consider this wrong. In fact one could argue that += is more appropriate, because we always add to options, and not replace previous assignments. If we output a debug message, we implicitly ask people to "fix" this, and we shouldn't. Also, all our rules use += right now.
2020-07-16udev: accept IMPORT{}= without any fussZbigniew Jędrzejewski-Szmek1-6/+2
Udev logs are full of messages about wrong operator type: ... Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules /usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:30 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:54 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:57 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:60 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:63 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:66 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:67 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:93 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:107 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:110 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-storage.rules:113 IMPORT key takes '==' or '!=' operator, assuming '=='. Reading rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules /usr/lib/udev/rules.d/60-persistent-v4l.rules:7 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-v4l.rules:9 IMPORT key takes '==' or '!=' operator, assuming '=='. /usr/lib/udev/rules.d/60-persistent-v4l.rules:16 IMPORT key takes '==' or '!=' operator, assuming '=='. ... The warning was downgraded in f0beb6f816035e438d684cc52ae76fc4a44fc197, but I think it should be removed altogether. IMPORT{program}="asdf" seems like an obvious way to write this, and people don't expect to have to write "==". So let's just allow any operator.
2020-07-16network: ndisc: any failures in processing event make the link in failed stateYu Watanabe1-111/+107
Also adjust log levels.
2020-07-16network: radv: clean up conf parsersYu Watanabe2-56/+41
2020-07-16network: downgrade log level in conf parsersYu Watanabe55-754/+864
2020-07-16nspawn: mount os-release in two steps to make it read-onlyLuca Boccassi2-3/+9
The kernel interface requires setting up read-only bind-mounts in two steps, the bind first and then a read-only remount. Fix nspawn-mount, and cover this case in the integration test. Fixes #16484
2020-07-16nspawn: use access/F_OK instead of stat to check for file existenceLuca Boccassi1-2/+1
2020-07-16shared/os-util: fix comment style to follow guidelinesLuca Boccassi1-1/+1
2020-07-16basic/mkdir: use uid_is_valid instead of manual checkLuca Boccassi1-2/+2
2020-07-16man: configuration files contain assignments, no directoriesLennart Poettering1-3/+2
2020-07-16man: GNOME is usually capitalizedLennart Poettering1-1/+1
2020-07-16man: don't claim environment.d/ was about sessionsLennart Poettering1-1/+1
This only sets the environment for user *services*, it has no effect on sessions, as those get an env block set up by whatever program sets them up and not systemd.
2020-07-16Revert "selinux: cache enforced status and treat retrieve failure as ↵Lennart Poettering3-36/+6
enforced mode" This reverts commit 257188f80ce1a083e3a88b679b898a73fecab53b.
2020-07-16machine: fix if checkLennart Poettering1-1/+1
Fixes: coverity 1430462
2020-07-16execute: fix if checkLennart Poettering1-1/+1
Fixes: coverity 1430459
2020-07-16dhcp4: only renewing lease when the client already has a leaseYu Watanabe1-1/+1
Follow-up for ceaec54a3c8366e81863a7d0d9c1f1d9f09960e1. Hopefully fixes #16299.
2020-07-16load-fragment: downgrade log messages we ignore to LOG_WARNINGLennart Poettering1-2/+2
We typically don't log above LOG_WARNING about issues we then go on to ignore. Do so here, too
2020-07-16mountpoint-util: fix error handlingLennart Poettering1-1/+1
2020-07-16network: dhcp4: add two warningsYu Watanabe1-4/+8
2020-07-16network: dhcp4: fix another race with SendDecline=yesYu Watanabe2-41/+66
If the SD_IPV4ACD_EVENT_BIND event happens before all routes are assigned, then the link stuck in configuring state.
2020-07-16network: dhcp4: also release old lease in dhcp_lease_lost()Yu Watanabe3-4/+4
The lease lost may happen during renewing address. If it happens, assertion hits in dhcp4_release_old_lease().
2020-07-16core: fix invalid assertionLennart Poettering1-2/+4
We miscounted here, and would hit an assert once too early.
2020-07-16network: fix typoChristian Göttsche1-1/+1
2020-07-15update TODOLennart Poettering1-0/+6
2020-07-15network: drop doubled white spaceYu Watanabe6-7/+7
2020-07-15network: free address when it is removedYu Watanabe1-0/+2
2020-07-15network: dhcp4: do not assign new address before old one is not removedYu Watanabe2-147/+241
If DHCP4 client lost a lease, and then soon acquire new lease, then the removal of the old address may not be completed. If that happens, and the new and old addresses are the same, then the new address will be considered as a foreign address. Such a situation can occur when the DHCP4 server is restarted. This makes networkd wait for the removal of the old address when a new lease is acquired. This also makes the link in configuring state when renewing address.
2020-07-15network: do not call link_check_ready() in ↵Yu Watanabe1-3/+2
link_request_set_routing_policy_rule() It will be called in link_request_set_nexthop() or serveral handlers().
2020-07-15network: make link_request_set_nexthop() called from ↵Yu Watanabe5-16/+28
link_request_set_routes() or route_handler() Then we can drop static_routes_ready() flag.
2020-07-15network: do not make link in configured state when no address is assignedYu Watanabe1-0/+5
When DHCP6 and RA are enabled, and RA does not provide any addresses, then link may become configured state even if no address is assigned, due to the time-lag between RA completion and DHCP reply. This makes if DHCP is explicitly enabled, then link must have at least one valid address to be in the configured state.
2020-07-15network: ndisc: split ndisc_configured flag into for addresses and routesYu Watanabe3-34/+52
2020-07-15network: ndisc: do not ignore remaining addressesYu Watanabe1-2/+1
Follow-up for c24c83dc67a63c88b0a537f4fa7f605b1fcbac39.
2020-07-15test-network: wait for addresses are not in tentative stateYu Watanabe2-2/+2
2020-07-15network: add debugging log why link is not in configured state yetYu Watanabe1-20/+59
2020-07-15test-network: check assigned address is not tentative stateYu Watanabe1-0/+6
2020-07-15test-network: set IPv6AcceptRA=no if no dynamic addresses are not requiredYu Watanabe34-0/+53
2020-07-15network: make link_request_set_nexthop() staticYu Watanabe2-2/+1
2020-07-15network: add a debugging logYu Watanabe1-0/+1
2020-07-15network: include error code in the log messageYu Watanabe1-7/+6
2020-07-15network: set dhcp6_xxx_configured flag after routes/addresses are assignedYu Watanabe4-32/+105
2020-07-15logs: when embedding catalog info in log output use a dash of color and unicodeLennart Poettering1-3/+22
let's separate things out a bit, to make it easier to discern log output and catalog data. catalog data is now colored green (which is a color we don't use for log data currently), and prefixed with a block shade.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-12 23:48:19 +0100