summaryrefslogtreecommitdiffstats
path: root/test/TEST-10-ISSUE-2467 (unfollow)
Commit message (Collapse)AuthorFilesLines
2019-04-27hwdb: add ACCEL_LOCATION property to parse_hwdb.pyLuís Ferreira1-0/+7
Signed-off-by: Luís Ferreira <contact@lsferreira.net>
2019-04-27hwdb: add ACCEL_LOCATION to the allowed propertiesLuís Ferreira1-0/+6
Signed-off-by: Luís Ferreira <contact@lsferreira.net>
2019-04-26nspawn-expose-ports: fix a typo in error messageBen Boeckel1-1/+1
2019-04-26resolve: use bridge or bonding interfaces in degraded-carrier stateYu Watanabe1-1/+1
Fixes #12285.
2019-04-26sd-bus: bump message queue size againFranck Bui1-2/+2
Simliarly to issue #4068, the current limit turns out to be too small for a big storage setup that uses many small disks. Let's bump it further.
2019-04-26udevd: notify when max number value of children is reached only once per ↵Franck Bui1-1/+10
batch of events When booting with "udev.log-priority=debug" for example, the output might be spammed with messages like this: systemd-udevd[23545]: maximum number (248) of children reached systemd-udevd[23545]: maximum number (248) of children reached systemd-udevd[23545]: maximum number (248) of children reached systemd-udevd[23545]: maximum number (248) of children reached systemd-udevd[23545]: maximum number (248) of children reached systemd-udevd[23545]: maximum number (248) of children reached systemd-udevd[23545]: maximum number (248) of children reached While the message itself is useful, printing it per batch of events should be enough.
2019-04-26chown-recursive: also check mode before we bypassLennart Poettering1-5/+5
2019-04-26json: let's not accept embedded NUL bytes when allocating JSON stringsLennart Poettering2-3/+7
Let's add an additional paranoia check, and not accept embedded NUL bytes in strings, just in case.
2019-04-26json: make log message more focussedLennart Poettering1-1/+1
2019-04-26bash-completion: accept files for --bind/--bind-ro optionsFrantisek Sumsal1-2/+2
2019-04-26bash-completion: process only non-template units for systemctl isolateFrantisek Sumsal1-1/+1
2019-04-26bash-completion: don't sort syslog prioritiesFrantisek Sumsal1-0/+1
By default, the available completions are sorted alphabetically, which is counterproductive in case of syslog priorities. Override the default behavior using the `nosort` option
2019-04-26Document /etc/initrd-releaseJérémy Rosen1-1/+3
When systemd is started, it detects initrd by checking for that file The usage of that file is not documented anywhere, so mention it early in the most relevant man-page I could find.
2019-04-25Revert "Revert "README: remove Coverity Scan badge""Evgeny Vereshchagin1-1/+0
This reverts commit 93e4163e912b6895e61c43452a629f30a28eb70c.
2019-04-25run: when we determine a timer cannot elapse anymore, really just warn, ↵Lennart Poettering1-11/+12
nothing else When we determine that a calendar expression cannot elapse anymore, print a warning but proceed regardless like we normally would. Quite possibly a remote system has a different understanding of time (timezone, system clock) than we have, hence we really shouldn't change behaviour here client side, but log at best, and then leave the decision what to do to the server side. Follow-up for #12299
2019-04-25calendarspec: make return time value of calendar_spec_next_usec() optionalLennart Poettering1-7/+12
If noone is interested, there's no reason to return it. (Also document the ENOENT error code in a comment)
2019-04-25run: check if the specified calendar event is not in the pastFrantisek Sumsal1-1/+19
Check if calendar event specification passed by --on-calendar runs in some time in the future. If not, execute the given command immediately
2019-04-25network: drop "return 1" when the return value is ignored by all callersZbigniew Jędrzejewski-Szmek1-3/+3
The reader is tricked into thinking that this has some meaning...
2019-04-25core: adjust unit_get_ancestor_memory_{low,min}() to work with units which ↵Zbigniew Jędrzejewski-Szmek1-6/+3
don't have a CGroupContext Coverity doesn't like the fact that unit_get_cgroup_context() returns NULL for unit types that don't have a CGroupContext. We don't expect to call those functions with such unit types, so this isn't an immediate problem, but we can make things more robust by handling this case. CID #1400683, #1400684.
2019-04-25hwdb: add axis range corrections for the Dell Latitude e7250Dave Ross1-0/+7
Based on touchpad-edge-detector and dimensions confirmed with the owner's manual (https://content.etilize.com/User-Manual/1037738079.pdf)
2019-04-25network: fix ref/unref logic for Link objectYu Watanabe3-57/+61
- bridge or bonding master takes a reference of slave links. - drop link from bridge or bonding master's slave list when slave link is removed. - change type of Link::slaves to Set*, Fixes #12315.
2019-04-25network: prevent interfaces to be initialized multiple timesYu Watanabe2-11/+17
When a uevent is received during the relevant interface is in LINK_STATE_PENDING, then the interface may be initialized twice. To prevent that, this introduces LINK_STATE_INITIALIZED.
2019-04-25udev,network: warn when .link or .network file has no [Match] sectionYu Watanabe6-5/+34
Closes #12098.
2019-04-25network: fix ListenPort= in [WireGuard] sectionYu Watanabe1-9/+10
This fixes a bug introduced by f1368a333e5e08575f0b45dfe41e936b106a8627. Fixes #12377.
2019-04-25test-network: fix invalid assertionsYu Watanabe1-23/+23
2019-04-24bash-completion: unify indentationFrantisek Sumsal1-1/+1
2019-04-24bash-completion: properly autocomplete escaped unit namesFrantisek Sumsal2-2/+11
2019-04-24NEWS: List getty@tty1.service as not being enabled anymorePaul Menzel1-2/+3
Fixes: https://github.com/systemd/systemd/issues/12345
2019-04-24man: describe interaction with ProtectHome=/InaccessiblePaths= in BindMount=Zbigniew Jędrzejewski-Szmek1-13/+22
https://github.com/systemd/systemd/issues/7153#issuecomment-485252308 Apparently this is still confusing for people. Longer-term, I think we should just make BindMount= automatically "upgrade" (or "downgrade", depending on how you look at this), any InaccessiblePath= mountpoints to "tmpfs". I don't see much point in forcing users to remember this interaction. But let's at least document the status quo, we can always update the docs if the code changes.
2019-04-24core: immediately trigger watchdog action on WATCHDOG=triggerJan Klötzke2-2/+31
A service might be able to detect errors by itself that may require the system to take the same action as if the service locked up. Add a WATCHDOG=trigger state change notification to sd_notify() to let the service manager know about the self-detected misery and instantly trigger the configured watchdog behaviour.
2019-04-24semaphore: merge semaphore scripts to avoid code duplication (#12365)Frantisek Sumsal3-104/+111
2019-04-23meson: do not use f-stringsZbigniew Jędrzejewski-Szmek1-2/+2
Our travis CI still uses python3.5. I'm making this into a separate commit to make it easy to revert later.
2019-04-23man: document sd_bus_add_{object,fallback}_vtableZbigniew Jędrzejewski-Szmek5-0/+613
The interface provided by those two functions is huge, so this text could probably be made two or three times as long if all details were described. But I think it's a good start.
2019-04-23sd-bus: when running user find function don't trust the value to be initializedZbigniew Jędrzejewski-Szmek1-1/+1
The find function is externally provided, and we shouldn't trust that the authors remember to set the output parameter in all cases.
2019-04-23busctl: add introspect --xml-interfaceZbigniew Jędrzejewski-Szmek2-0/+23
This wraps the call to org.freedesktop.DBus.Introspectable.Introspect. Using "busctl call" directly is inconvenient because busctl escapes the string before printing. Example: $ busctl introspect --xml org.freedesktop.systemd1 /org/freedesktop/systemd1 | pygmentize -lxml | less -RF
2019-04-23test-bus-{vtable,introspect}: share data and test introspect_path()Zbigniew Jędrzejewski-Szmek6-142/+178
test-bus-introspect is also applied to the tables from test-bus-vtable.c. test-bus-vtable.c is also used as C++ sources to produce test-bus-vtable-cc, and our hashmap headers are not C++ compatible. So let's do the introspection part only in the C version.
2019-04-23basic/socket-util: put a limit on the loop to flush connectionsZbigniew Jędrzejewski-Szmek1-1/+9
Follow-up for #12346.
2019-04-23hwdb: Fix the key codes of the OLPC XO button padLubomir Rintel1-8/+8
These are not on a key pad. These codes are sent by the "rocker" buttons that resemble a game pad.
2019-04-23hwdb: Fix the OLPC XO rotate keyLubomir Rintel1-1/+1
The comment is incorrect -- this key code is sent by the rotate button, the brightness keys are separate.
2019-04-23hwdb: No LEDs on the OLPC XO keyboardLubomir Rintel1-0/+2
2019-04-23hwdb: Make the OLPC XO rules also match XO-1.75Lubomir Rintel1-1/+3
Uses the same keyboard, attached to the "Security Processor" P1J core that bit-bangs the PS/2 keyboard protocol.
2019-04-23basic/socket-util: fix typo and reword commentZbigniew Jędrzejewski-Szmek1-7/+7
Comment bike-shedding might be the ultimate form of procrastination, but I can't stop myself. :)
2019-04-23catalog: update Polish translationPiotr Drąg1-0/+14
2019-04-23udev: net_id: introduce predictable names for netdevsimJiri Pirko3-0/+53
In order to properly and predictably name netdevsim netdevices, introduce a separate implementation, as the netdevices reside on a specific netdevsim bus. Note that this applies only to netdevsim devices created using sysfs, because those expose phys_port_name attribute. Signed-off-by: Jiri Pirko <jiri@mellanox.com>
2019-04-23udev-rules: add udmabuf to kvm groupMarc-André Lureau1-0/+2
It will have the default 0660 mode. Fixes: #12283 Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2019-04-23sd-bus: split introspection into the content creation and reply creation partsZbigniew Jędrzejewski-Szmek5-41/+75
Just moving code around, in preparation to allow the content creation part to be used in other places. On the surface of things, introspect_path() should be in bus-introspect.c, but introspect_path() uses many static helper functions in bus-objects.c, so moving it would require all of them to be exposed, which is too much trouble. test-bus-introspect is updated to actually write the closing bracket.
2019-04-23sd-bus: use _cleanup_ for struct introspectZbigniew Jędrzejewski-Szmek2-30/+15
2019-04-23sd-bus: allow vtable format structure to grow in the futureZbigniew Jędrzejewski-Szmek2-18/+15
We would check the size of sd_bus_vtable entries, requring one of the two known sizes. But we should be able to extend the structure in the future, by adding new fields, without breaking backwards compatiblity. Incidentally, this check was what caused -EINVAL failures before, when programs were compiled with systemd-242 and run with older libsystemd.
2019-04-23sd-bus: add symbol to tell linker that new vtable functions are usedZbigniew Jędrzejewski-Szmek4-6/+30
In 856ad2a86bd9b3e264a090fcf4b0d05bfaa91030 sd_bus_add_object_vtable() and sd_bus_add_fallback_vtable() were changed to take an updated sd_bus_vtable[] array with additional 'features' and 'names' fields in the union. The commit tried to check whether the old or the new table format is used, by looking at the vtable[0].x.start.element_size field, on the assumption that the added fields caused the structure size to grow. Unfortunately, this assumption was false, and on arm32 (at least), the structure size is unchanged. In libsystemd we use symbol versioning and a major.minor.patch semantic versioning of the library name (major equals the number in the so-name). When systemd-242 was released, the minor number was (correctly) bumped, but this is not enough, because no new symbols were added or symbol versions changed. This means that programs compiled with the new systemd headers and library could be successfully linked to older versions of the library. For example rpm only looks at the so-name and the list of versioned symbols, completely ignoring the major.minor numbers in the library name. But the older library does not understand the new vtable format, and would return -EINVAL after failing the size check (on those architectures where the structure size did change, i.e. all 64 bit architectures). To force new libsystemd (with the functions that take the updated sd_bus_vtable[] format) to be used, let's pull in a dummy symbol from the table definition. This is a bit wasteful, because a dummy pointer has to be stored, but the effect is negligible. In particular, the pointer doesn't even change the size of the structure because if fits in an unused area in the union. The number stored in the new unsigned integer is not checked anywhere. If the symbol exists, we already know we have the new version of the library, so an additional check would not tell us anything. An alternative would be to make sd_bus_add_{object,fallback}_vtable() versioned symbols, using .symver linker annotations. We would provide sd_bus_add_{object,fallback}_vtable@LIBSYSTEMD_221 (for backwards compatibility) and e.g. sd_bus_add_{object,fallback}_vtable@@LIBSYSTEMD_242 (the default) with the new implementation. This would work too, but is more work. We would have to version at least those two functions. And it turns out that the .symver linker instructions have to located in the same compilation unit as the function being annotated. We first compile libsystemd.a, and then link it into libsystemd.so and various other targets, including libsystemd-shared.so, and the nss modules. If the .symver annotations were placed next to the function definitions (in bus-object.c), they would influence all targets that link libsystemd.a, and cause problems, because those functions should not be exported there. To export them only in libsystemd.so, compilation would have to be rearranged, so that the functions exported in libsystemd.so would not be present in libsystemd.a, but a separate compilation unit containg them and the .symver annotations would be linked solely into libsystemd.so. This is certainly possible, but more work than the approach in this patch. 856ad2a86bd9b3e264a090fcf4b0d05bfaa91030 has one more issue: it relies on the undefined fields in sd_bus_vtable[] array to be zeros. But the structure contains a union, and fields of the union do not have to be zero-initalized by the compiler. This means that potentially, we could have garbarge values there, for example when reading the old vtable format definition from the new function implementation. In practice this should not be an issue at all, because vtable definitions are static data and are placed in the ro-data section, which is fully initalized, so we know that those undefined areas will be zero. Things would be different if somebody defined the vtable array on the heap or on the stack. Let's just document that they should zero-intialize the unused areas in this case. The symbol checking code had to be updated because otherwise gcc warns about a cast from unsigned to a pointer.
2019-04-22core: support DisableControllers= for transient unitsAnita Zhang4-9/+31
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-12 23:55:04 +0100