summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* core: print warning on invalid swap pri= fieldZbigniew Jędrzejewski-Szmek2015-03-13
| | | | CID #1264371.
* core: one more (void)Zbigniew Jędrzejewski-Szmek2015-03-13
| | | | CID #996308.
* logind: explicitly ignore errors we can do nothing aboutZbigniew Jędrzejewski-Szmek2015-03-13
| | | | CID #1237545.
* bus: explicitly ignore failure during error handlingZbigniew Jędrzejewski-Szmek2015-03-13
| | | | CID #1237548.
* core: explicitly ignore failure during cleanupZbigniew Jędrzejewski-Szmek2015-03-13
| | | | CID #1237550.
* core: don't wait for reply if writing to pipe failsZbigniew Jędrzejewski-Szmek2015-03-13
| | | | | | | This shouldn't really happen, but it's seems cleaner to continue on error. CID #1237552.
* core: either ignore or handle mount failuresZbigniew Jędrzejewski-Szmek2015-03-13
| | | | | | | | /dev/pts/ptmx is as important as /dev/pts, so error out if that fails. Others seem less important, since the namespace is usable without them, so ignore failures. CID #123755, #123754.
* Use space after a silencing (void)Zbigniew Jędrzejewski-Szmek2015-03-13
| | | | | We were using a space more often than not, and this way is codified in CODING_STYLE.
* core: ignore any issues with setting time on jobs_in_progress_event_sourceZbigniew Jędrzejewski-Szmek2015-03-13
| | | | CID #1237559.
* sd-resolve: use different element of union to make code more readableZbigniew Jędrzejewski-Szmek2015-03-13
| | | | | | They both point to the same location, but the reader is not forced to look back to the beginning of the function to see that.
* journal-remote: explain why source->buf cannot be nullZbigniew Jędrzejewski-Szmek2015-03-13
| | | | In reference to CID #1238956.
* Check that EWOULDBLOCK is the same as EAGAINZbigniew Jędrzejewski-Szmek2015-03-13
| | | | | | It certainly is everywhere on Linux, but as a courtesy to people doing some strange cross-compilation, check that the assumption holds.
* journal-remote: make process_data staticZbigniew Jędrzejewski-Szmek2015-03-13
|
* nspawn: tell coverity that we ignore return valueZbigniew Jędrzejewski-Szmek2015-03-13
| | | | CID #1271353.
* gpt-auto-generator: allow type check to failZbigniew Jędrzejewski-Szmek2015-03-13
| | | | | add_mount() is OK with unknow file type, but we have to initalize the variable to NULL not to pass garbage on error.
* efi: widen operand to avoid overflowZbigniew Jędrzejewski-Szmek2015-03-13
| | | | CID #1287141.
* core: issue error on oom we can do nothing aboutZbigniew Jędrzejewski-Szmek2015-03-13
| | | | CID #1287142.
* µhttp-util: setup gnutls logs in one functionZbigniew Jędrzejewski-Szmek2015-03-13
|
* udev: make set_usec_initialized() internal to libudevTom Gundersen2015-03-13
| | | | | Instead introduce ensure_usec_initialized(), which copies the timestamp if possible otherwise sets it to now(CLOCK_MONOTONIC).
* sd-rtnl: read_message - don't set group if not neededTom Gundersen2015-03-13
|
* sd-rtnl: process - only apply matches to broadcast messagesTom Gundersen2015-03-13
|
* sd-rtnl: improve detection of broadcast messagesTom Gundersen2015-03-13
| | | | | | Do not rely on nl_pid == 0, but check the groups instead. We currently avoid using nl_pid == 0 for unicast anyway, so this should be redundant, but let's try to be correct.
* sd-rtnl: never set serial to 0Tom Gundersen2015-03-13
| | | | | | | In the unlikely event that we wrap the counter, skip 0 as this is used for broadcasts. Suggested by Richard Maw.
* tree-wide: there is no ENOTSUP on linuxDavid Herrmann2015-03-13
| | | | Replace ENOTSUP by EOPNOTSUPP as this is what linux actually uses.
* bus: stop using EDEADLOCKDavid Herrmann2015-03-13
| | | | | | | The error code is called EDEADLK, stop using legacy names like EDEADLOCK. Note that _some_ weird architectures define them differently (namely, mips and sparc), but on all sane architectures they're exactly the same. So stay with the widely used code, which is EDEADLK.
* journal-remote: stop using EWOULDBLOCKDavid Herrmann2015-03-13
| | | | | There is no reason to ever use EWOULDBLOCK. It's equivalent to EAGAIN on all architectures on linux.
* udev: dont use EWOULDBLOCKDavid Herrmann2015-03-13
| | | | EWOULDBLOCK is the same as EAGAIN, stop using it.
* gpt-auto-generator: fix detection of /srvMathieu Chevrier2015-03-13
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=89226
* sd-event: fix typoZbigniew Jędrzejewski-Szmek2015-03-13
|
* journal-remote: process events without delayZbigniew Jędrzejewski-Szmek2015-03-13
| | | | | | | | | | | | | | | | | | journal-remote buffers input, and then parses it handling one journal entry at a time. It was possible for useful data to be left in the buffer after some entries were processesed. But all data would be already read from the fd, so there would be no reason for the event loop to call the handler again. After some new data came in, the handler would be called again, and would then process the "old" data in the buffer. Fix this by enabling a handler wherever we process input data and do not exhaust data from the input buffer (i.e. when EAGAIN was not encountered). The handler runs until we encounter EAGAIN. Looping over the input data is done in this roundabout way to allow the event loop to dispatch other events in the meanwhile. If the loop was inside the handler, a source which produced data fast enough could completely monopolize the process. https://bugs.freedesktop.org/show_bug.cgi?id=89516
* journal-remote: check also for EWOULDBLOCKZbigniew Jędrzejewski-Szmek2015-03-13
| | | | This matches similar code elsewhere.
* journal-remote: downgrade routine messages to debugZbigniew Jędrzejewski-Szmek2015-03-13
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=89486
* sd-pppoe: workaround for incomplete include in old kernelsZbigniew Jędrzejewski-Szmek2015-03-12
|
* networkd: Begin with serial number 1 for netlink requestsRichard Maw2015-03-12
| | | | | | | | | | | | | | | | | | | | | "Notifications are of informal nature and no reply is expected, therefore the sequence number is typically set to 0."[1] If networkd is started soon after recent netlink activity, then there will be messages with sequence number 0 in the buffer. The first thing networkd does is to request a dump of all the links. If it uses sequence number 0 for this, then it may confuse the dump request's response with that of a notification. This will result in it failing to properly enumerate all the links, but more importantly, when it comes to enumerate all the addresses, it will still have the link dump in progress, so the address enumeration will fail with -EBUSY. [1]: http://www.infradead.org/~tgr/libnl/doc/core.html#core_msg_types [tomegun: sequence -> serial]
* core: add missing words to my fix of explanation of associativityTom Gundersen2015-03-12
|
* udevd: improve handling of failed workerTom Gundersen2015-03-12
| | | | | | The information in the db is stale, so it does not make sense to expose it any longer. Also, don't drop the kernel event, but simply pass it on to userspace without ammending it.
* udevd: don't free event when killing the worker, wait until it has been reapedTom Gundersen2015-03-12
| | | | This will allow us to clean up the device when we are notified about the worker being killed.
* libudev: introduce clone_with_db()Tom Gundersen2015-03-12
| | | | This allows us to move the db reading from udevd to libudev.
* libudev: monitor - fix error path in send_deviceTom Gundersen2015-03-12
| | | | Return -errno rather than -1 in case sendmsg() fails.
* udevd: event - make db loading lazy in REMOVE event handlingTom Gundersen2015-03-12
| | | | | | | | | We were explicitly eagerly loading the db, then deletenig the backing file and then processing the rules/symlinks. Instead we delete the backnig db file as the last step and let the db loading be lazy as everywhere else. This may save us a bit of work in casese where the db is not needed, but more importantly it hides some implementation details of libudev-device form udevd.
* libudev: introduce udev_device_properties_copy()Tom Gundersen2015-03-12
| | | | To copy properties from one device to another. Drop the equivalent functionality from udevd.
* boot: efi - add config option to disable the command line editorKay Sievers2015-03-11
|
* cgtop: fix assert when not on ttyUmut Tezduyar Lindskog2015-03-11
| | | | | | | | | | systemd-cgtop --dept=1 -b -n 10 -d 0.1 | cat Assertion 'new_length >= 3' failed at src/shared/util.c:3 \ 595, function ellipsize_mem(). Aborting. Aborted (core dumped) (David: add comment)
* core: fix cgroups-agent match for kdbusDavid Herrmann2015-03-11
| | | | | | On kdbus, we get cgroups-agent messages via the system bus, not the private systemd socket. Therefore, we must install the match properly or we will never receive cgroup notifications.
* core: rewind message before forwarding itDavid Herrmann2015-03-11
| | | | | | Forwarding messages that are not rewinded will drop data. Fix this for cgroups-agent messages that we might remarshal before forwarding to the system bus.
* bus: remarshal kdbus messages received from the kernelDavid Herrmann2015-03-11
| | | | | | If we receive an sd_bus_message from the kernel, m->kdbus will contain additional items that cannot be used when sending a message. Therefore, always remarshal the message if it is used again.
* bus: drop redundant assignmentDavid Herrmann2015-03-11
| | | | | This assignment is already done in the parent context, no need to do it again.
* socket-util: refactor error handling in sockaddr_prettyZbigniew Jędrzejewski-Szmek2015-03-11
|
* core: fix explanation of associativityTom Gundersen2015-03-11
|
* bus-proxy: complain only once about queue overflowsDavid Herrmann2015-03-11
| | | | | | | | | | | | | | | | | | | | | If the local peer does not dispatch its incoming queue, the bus-proxy will slowly fill its outgoing queue. Once its full, it will continously complain that it cannot forward its messages. As it turns out, pulseaudio does have an idle background dbus connection that is not integrated into any mainloop (and given that gdbus and libdbus1 both support background shared connections, PA is probably not the only example), therefore, the bus-proxy will loudly complain if it cannot forward NameOwnerChanged events once the queue is full. This commit makes the proxy track queue-state and complain only once the queue runs full, not if it is already full. A PA bug-report (and patch) has been filed, and other applications should be fixed similarly. Hence, lets keep the error message, instead of dropping it. It's unused resources we really want to get rid of, so silencing the message does not really help (which is actually what dbus-daemon does).
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-26 01:13:23 +0000