chiark / gitweb /
6 years agoshared - reinstate plymouth_running()
Tom Gundersen [Mon, 16 Mar 2015 17:29:26 +0000 (18:29 +0100)]
shared - reinstate plymouth_running()

This will be used by fsckd. This reverts part of

6 years agocore: Remove explicit Plymouth integration
Jasper St. Pierre [Mon, 16 Mar 2015 16:34:59 +0000 (09:34 -0700)]
core: Remove explicit Plymouth integration

Even if plymouth is running, it might have not displayed the splash yet,
so we'll see a few lines on fbcon when we should have otherwise had

Plymouth integration was added to systemd in commit
6faa11140bf776cdaeb8d22d01816e6e48296971. That same day, Plymouth got
systemd integration [0]. As such, the Plymouth integration has always
been obsolete, and was probably only for older Plymouth's. But I can't
imagine anybody running a Plymouth from 2011 with a systemd from 2015.

Remove the Plymouth/systemd integration, and let Plymouth's code tell
systemd to print the details.


Signed-off-by: Jasper St. Pierre <>
Cc: Daniel Drake <>
Cc: Ray Strode <>
6 years agoRevert "hwdb: merge atkbd into platform matches"
David Herrmann [Mon, 16 Mar 2015 14:51:25 +0000 (15:51 +0100)]
Revert "hwdb: merge atkbd into platform matches"

This reverts commit ba76ee29bc02879fb42c048132af8889b00220d5. As it turns
out, we need to match on driver=atkbd to not load the fixups on any
plugged USB devices.

That is, whenever you use "name:<name>:dmi:<dmi>" style matches, you
better provide a name or you're screwing things up.

6 years agocore: don't change removed devices to state "tentative"
Martin Pitt [Fri, 13 Mar 2015 07:35:59 +0000 (08:35 +0100)]
core: don't change removed devices to state "tentative"

Commit 628c89c introduced the "tentative" device state, which caused
devices to go from "plugged" to "tentative" on a remove uevent. This
breaks the cleanup of stale mounts (see commit 3b48ce4), as that only
applies to "dead" devices.

The "tentative" state only really makes sense on adding a device when
we don't know where it was coming from (i. e. not from udev). But when
we get a device removal from udev we definitively know that it's gone,
so change the device state back to "dead" as before 628c89c.

6 years agorules: keyboard - remove "platform" from comments
Kay Sievers [Mon, 16 Mar 2015 12:43:50 +0000 (13:43 +0100)]
rules: keyboard - remove "platform" from comments

6 years agohwdb: merge atkbd into platform matches
David Herrmann [Mon, 16 Mar 2015 11:19:09 +0000 (12:19 +0100)]
hwdb: merge atkbd into platform matches

Currently, we always run
  hwdb 'keyboard:name:$attr{name}:$attr{[dmi/id]modalias}'
as last step to match keyboards. Therefore, if nothing else matched so
far, we still try the device-name+dmi combination.

However, we have a special atkbd rule which is only run for atkbd as:
  hwdb 'keyboard:$attr{[dmi/id]modalias}'

This is redundant, as we already pass the same information to hwdb in the
last fallback step.

This patch converts the hwdb "keyboard:dmi:*" matches to
"keyboard:name:*:dmi:*" matches and drops the redundant rule.

6 years agorules: drop redundant match
David Herrmann [Mon, 16 Mar 2015 11:05:36 +0000 (12:05 +0100)]
rules: drop redundant match

The 60-keyboard rules are already guared by KERNEL!="event*" bail-outs,
therefore, KERNELS="input*" is always true. Drop it!

6 years agohwdb: support bluetooth keyboard fixups
David Herrmann [Mon, 16 Mar 2015 11:04:38 +0000 (12:04 +0100)]
hwdb: support bluetooth keyboard fixups

Drop the restriction not to match on bluetooth devices. They are supported
just fine!

6 years agohwdb: convert to generic input-modalias matches
David Herrmann [Mon, 16 Mar 2015 11:00:46 +0000 (12:00 +0100)]
hwdb: convert to generic input-modalias matches

There is no reason to match on usb-modaliases, if we can use the
input-modalias to achieve the same. This commit changes the
keyboard-lookups to not be restricted to USB, but pass all modaliases to
the hwdb. Furthermore, we convert all usb:* matches to input:* matches,
thus getting rid of any ambiguity if multiple usb devices are chained (or
a bluetooth device / etc. is on top).

Note that legacy keyboard:usb:* matches are still supported, but
deprecated. If possible, please use keyboard:input:* matches instead.

This is a required step to make other input devices work with
60-keyboard.hwdb. Other bus-types are often chained on usb and we want to
avoid any ambiguity here if we incorrectly match on a USB hub.

6 years agopo: update Polish translation
Piotr Drąg [Sun, 15 Mar 2015 22:01:19 +0000 (23:01 +0100)]
po: update Polish translation

6 years agoman: standard-conf: change directory reference to wildcard
Alison Chaiken [Sun, 15 Mar 2015 23:26:14 +0000 (16:26 -0700)]
man: standard-conf: change directory reference to wildcard

6 years agovconsole-setup: check error of child process
Lucas De Marchi [Fri, 13 Mar 2015 17:47:28 +0000 (17:47 +0000)]
vconsole-setup: check error of child process

If we don't check the error of the child process, systemd-vconsole-setup
would exit with 0 even if it could not really setup the console.

For a simple test, move loadkeys elsewhere and execute

[root@localhost ~]# strace -f -e execve /usr/lib/systemd/systemd-vconsole-setup
execve("/usr/lib/systemd/systemd-vconsole-setup", ["/usr/lib/systemd/systemd-vconsol"...], [/* 15 vars */]) = 0
Process 171 attached
[pid   171] execve("/usr/bin/loadkeys", ["/usr/bin/loadkeys", "-q", "-C", "/dev/tty0", "br-abnt2"], [/* 15 vars */]) = -1 ENOENT (No such file or directory)
[pid   171] +++ exited with 1 +++
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=171, si_uid=0, si_status=1, si_utime=0, si_stime=0} ---
+++ exited with 0 +++

Note that loadkeys returned 1 while systemd-vconsole-setup return 0.

Since the font and keyboard setup are already serialized, refactor the
code a little bit so the functions do the wait by themselves. One change
in behavior in this patch is that we don't return early, but we do try
to setup the keyboard even if the font load failed.

6 years agonetwork: add UseNTP DHCP option
Michael Marineau [Fri, 13 Mar 2015 19:01:29 +0000 (12:01 -0700)]
network: add UseNTP DHCP option

Despite having the internal logic in place to enable/disable using NTP
servers provided by DHCP the network config didn't expose the option.

6 years agoAdd (void) where we don't care about return value
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 21:17:24 +0000 (17:17 -0400)]
Add (void) where we don't care about return value

6 years agojournal-gatewayd: factor out opening of temp file
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 21:13:43 +0000 (17:13 -0400)]
journal-gatewayd: factor out opening of temp file

Also use our own mkostemp wrapper, which tries to use O_TMPFILE.

6 years agologind: check return value of session_release
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 20:37:39 +0000 (16:37 -0400)]
logind: check return value of session_release

It allocates memory, so it can fail.

CID #1237527.

6 years agoutil: check asprintf return value
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 19:59:23 +0000 (15:59 -0400)]
util: check asprintf return value

CID #1237546.

6 years agocore: remove useless debug message
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 16:12:19 +0000 (12:12 -0400)]
core: remove useless debug message

Mar 13 19:48:28 systemd[1]: Collecting (null)
Mar 13 19:48:28 systemd[1]: Collecting (null)
Mar 13 19:48:28 systemd[1]: Collecting (null)
Mar 13 19:48:28 systemd[1]: Collecting (null)
Mar 13 19:48:28 systemd[1]: Collecting (null)
Mar 13 19:48:28 systemd[1]: Collecting (null)
Mar 13 19:48:28 systemd[1]: Collecting (null)

6 years agolibudev-monitor: use initialization
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 11:31:20 +0000 (07:31 -0400)]
libudev-monitor: use initialization

6 years agotimesyncd: enable timesyncd in virtual machines
Kay Sievers [Sun, 15 Mar 2015 18:44:59 +0000 (19:44 +0100)]
timesyncd: enable timesyncd in virtual machines

On Fri, Mar 13, 2015 at 8:25 PM, Michael Marineau <> wrote:
> Currently systemd-timesyncd.service includes
> ConditionVirtualization=no, disabling it in both containers and
> virtual machines. Each VM platform tends to deal with or ignore the
> time problem in their own special ways, KVM/QEMU has the kernel time
> source kvm-clock, Xen has had different schemes over the years, VMware
> expects a userspace daemon sync the clock, and other platforms are
> content to drift with the wind as far as I can tell.
> I don't know of a robust way to know if a platform needs a little
> extra help from userspace to keep the clock sane or not but it seems
> generally safer to try than to risk drifting. Does anyone know of a
> reason to leave timesyncd off by default? Otherwise switching to
> ConditionVirtualization=!container should be reasonable.

6 years agojournald: add syslog fields for audit messages
Zbigniew Jędrzejewski-Szmek [Wed, 4 Mar 2015 15:31:42 +0000 (10:31 -0500)]
journald: add syslog fields for audit messages

Audit messages would be displayed as "unknown[1]".

Also specify AUTH as facility... This seems to be the closest match
(/* security/authorization messages */).

6 years agosysctl: tweak debug message
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 02:56:01 +0000 (22:56 -0400)]
sysctl: tweak debug message

6 years agocryptsetup-generator: remove warning about crypttab access mode
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 02:35:30 +0000 (22:35 -0400)]
cryptsetup-generator: remove warning about crypttab access mode

This file contains no privileged data — just names of devices to decrypt
and files containing keys. On a running system most of this can be inferred from
the device tree anyway.

6 years agoudev: downgrade "has devpath" and "filled with db file" messages
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 02:22:49 +0000 (22:22 -0400)]
udev: downgrade "has devpath" and "filled with db file" messages

Udev debug messages have to be significantly overhauled... For now
just downgrade those two. They are responsible for approximately 25%
of debug output during boot and are rather useless.

6 years agogpt-auto-generator: prefix messages with device name
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 02:15:05 +0000 (22:15 -0400)]
gpt-auto-generator: prefix messages with device name

6 years agocore: do not use quotes around virt and arch
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 01:49:10 +0000 (21:49 -0400)]
core: do not use quotes around virt and arch

Quotes are useful when the string can contain spaces or be otherwise
confusing. Not possible with those two.

6 years agosysv-generator: initialize LookupPaths just once
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 01:46:59 +0000 (21:46 -0400)]
sysv-generator: initialize LookupPaths just once

With debugging on, sysv-generator would print the full set of
lookup paths for *every* sysv script.

While at it, pass LookupPaths as a pointer in sysv-generator,
and constify it everywhere.

6 years agotmpfiles: remove redundant debug message
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 00:24:47 +0000 (20:24 -0400)]
tmpfiles: remove redundant debug message

Mar 13 19:48:30 systemd-tmpfiles[970]: "/var/lib/machines" has right mode 40700
Mar 13 19:48:30 systemd-tmpfiles[970]: /var/lib/machines created successfully.

6 years agoutil: remove redundant debug message
Zbigniew Jędrzejewski-Szmek [Sun, 15 Mar 2015 00:14:39 +0000 (20:14 -0400)]
util: remove redundant debug message

mar 14 20:05:34 fedora22 systemd[4058]: /usr/lib/systemd/system-generators/ will be executed.
mar 14 20:05:34 fedora22 systemd[4058]: Spawned /usr/lib/systemd/system-generators/ as 4059.

The second line already says everything.

6 years agounits: there is no systemd-udev-hwdb-update.service
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 21:56:13 +0000 (17:56 -0400)]
units: there is no systemd-udev-hwdb-update.service

6 years agocore: remove left-over debug message
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 21:41:53 +0000 (17:41 -0400)]
core: remove left-over debug message

6 years agoservice: don't add After= dependencies on .busname units if kdbus support is disabled
Michael Biebl [Sat, 14 Mar 2015 15:48:54 +0000 (16:48 +0100)]
service: don't add After= dependencies on .busname units if kdbus support is disabled

6 years agoudev-ctrl: fix strict aliasing issues
Shawn Landden [Wed, 11 Mar 2015 04:01:47 +0000 (21:01 -0700)]
udev-ctrl: fix strict aliasing issues

it is ironic that
"The only purpose of this structure is to cast the structure pointer
passed in addr in order to avoid compiler warnings.  See EXAMPLE below."
from bind(2)

6 years agosd-dhcp-client: fix strict aliasing issue
Shawn Landden [Wed, 11 Mar 2015 03:45:15 +0000 (20:45 -0700)]
sd-dhcp-client: fix strict aliasing issue

6 years agoman: add sd_event_{run,wait,prepare,dispatch,loop}
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 01:35:32 +0000 (21:35 -0400)]
man: add sd_event_{run,wait,prepare,dispatch,loop}

6 years agosd-event: sd_event_run - only return 0 on timeout
Tom Gundersen [Sat, 14 Mar 2015 11:09:20 +0000 (12:09 +0100)]
sd-event: sd_event_run - only return 0 on timeout

sd_event_dispatch() returns 0 on FINISH, so let's eat that up.

6 years agosd-event: rename PASSIVE/PREPARED to INITIAL/ARMED
Tom Gundersen [Sat, 14 Mar 2015 10:47:35 +0000 (11:47 +0100)]

6 years agoselinux: fix SEGV during switch-root if SELinux policy loaded
Will Woods [Fri, 13 Mar 2015 21:24:46 +0000 (17:24 -0400)]
selinux: fix SEGV during switch-root if SELinux policy loaded

If you've got SELinux policy loaded, label_hnd is your labeling handle.
When systemd is shutting down, we free that handle via mac_selinux_finish().

But: switch_root() calls mkdir_p_label(), which tries to look up a label
using that freed handle, and so we get a bunch of garbage and eventually
SEGV in libselinux.

(This doesn't happen in the switch-root from initramfs to real root because
there's no SELinux policy loaded in initramfs, so label_hnd is NULL and we
never attempt any lookups.)

So: make sure that mac_selinux_finish() actually sets label_hnd to NULL, so
nobody tries to use it after it becomes invalid.

6 years agoman: fix indentation of copyright headers
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:26:47 +0000 (21:26 -0500)]
man: fix indentation of copyright headers

6 years agoman: no paren in link
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:26:34 +0000 (21:26 -0500)]
man: no paren in link

6 years agoman: fix name of systemd.journal-fields(7)
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:26:20 +0000 (21:26 -0500)]
man: fix name of systemd.journal-fields(7)

6 years agoman: fix link to strerror(3)
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:26:06 +0000 (21:26 -0500)]
man: fix link to strerror(3)

6 years agoman: s/sd_bus_message_get_seqno/sd_bus_message_get_seqnum/
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:25:52 +0000 (21:25 -0500)]
man: s/sd_bus_message_get_seqno/sd_bus_message_get_seqnum/

6 years agoman: fix name of systemd.resource-control(5)
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:25:37 +0000 (21:25 -0500)]
man: fix name of systemd.resource-control(5)

6 years agoman: link to fd.o for dbus stuff
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:24:30 +0000 (21:24 -0500)]
man: link to fd.o for dbus stuff

6 years agoman: link to for inetd(8)
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:23:24 +0000 (21:23 -0500)]
man: link to for inetd(8)

6 years agoman: fix a bunch of links
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:22:39 +0000 (21:22 -0500)]
man: fix a bunch of links

All hail linkchecker!

6 years agosd-daemon: simplify sd_pid_notify_with_fds
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:22:05 +0000 (21:22 -0500)]
sd-daemon: simplify sd_pid_notify_with_fds

Coverity was complaining that CMSG_NXTHDR is used without
checking the return value. In this case it cannot fail, but
it is a good excuse to simplify the function a bit.

CID #1261726.

6 years agoudev: properly calculate size of remaining data
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:22:02 +0000 (21:22 -0500)]
udev: properly calculate size of remaining data

The data comes from the kernel, so chances of it being
garbled are low, but for correctness' sake, add the check.

CID #996458.

6 years agotest-dhcp-option: conform to usual coding style
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:22:00 +0000 (21:22 -0500)]
test-dhcp-option: conform to usual coding style

6 years agotest-dhcp-option: add assert to check index is nonnegative
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:21:58 +0000 (21:21 -0500)]
test-dhcp-option: add assert to check index is nonnegative

CID #1237623.

6 years agocore: check asprintf return value
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:21:52 +0000 (21:21 -0500)]
core: check asprintf return value

CID #1261729.

6 years agocore: print warning on invalid swap pri= field
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:21:46 +0000 (21:21 -0500)]
core: print warning on invalid swap pri= field

CID #1264371.

6 years agocore: one more (void)
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:21:41 +0000 (21:21 -0500)]
core: one more (void)

CID #996308.

6 years agologind: explicitly ignore errors we can do nothing about
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:21:38 +0000 (21:21 -0500)]
logind: explicitly ignore errors we can do nothing about

CID #1237545.

6 years agobus: explicitly ignore failure during error handling
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:21:05 +0000 (21:21 -0500)]
bus: explicitly ignore failure during error handling

CID #1237548.

6 years agocore: explicitly ignore failure during cleanup
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:20:59 +0000 (21:20 -0500)]
core: explicitly ignore failure during cleanup

CID #1237550.

6 years agocore: don't wait for reply if writing to pipe fails
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:20:53 +0000 (21:20 -0500)]
core: don't wait for reply if writing to pipe fails

This shouldn't really happen, but it's seems cleaner to
continue on error.

CID #1237552.

6 years agocore: either ignore or handle mount failures
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:20:47 +0000 (21:20 -0500)]
core: either ignore or handle mount failures

/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.

6 years agoUse space after a silencing (void)
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:20:01 +0000 (21:20 -0500)]
Use space after a silencing (void)

We were using a space more often than not, and this way is
codified in CODING_STYLE.

6 years agocore: ignore any issues with setting time on jobs_in_progress_event_source
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:11:09 +0000 (21:11 -0500)]
core: ignore any issues with setting time on jobs_in_progress_event_source

CID #1237559.

6 years agosd-resolve: use different element of union to make code more readable
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:11:05 +0000 (21:11 -0500)]
sd-resolve: use different element of union to make code more readable

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.

6 years agojournal-remote: explain why source->buf cannot be null
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:11:03 +0000 (21:11 -0500)]
journal-remote: explain why source->buf cannot be null

In reference to CID #1238956.

6 years agoCheck that EWOULDBLOCK is the same as EAGAIN
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:10:19 +0000 (21:10 -0500)]
Check that EWOULDBLOCK is the same as EAGAIN

It certainly is everywhere on Linux, but as a courtesy
to people doing some strange cross-compilation, check
that the assumption holds.

6 years agojournal-remote: make process_data static
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:10:17 +0000 (21:10 -0500)]
journal-remote: make process_data static

6 years agonspawn: tell coverity that we ignore return value
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:10:15 +0000 (21:10 -0500)]
nspawn: tell coverity that we ignore return value

CID #1271353.

6 years agogpt-auto-generator: allow type check to fail
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:10:13 +0000 (21:10 -0500)]
gpt-auto-generator: allow type check to fail

add_mount() is OK with unknow file type, but we have to initalize
the variable to NULL not to pass garbage on error.

6 years agoefi: widen operand to avoid overflow
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:10:12 +0000 (21:10 -0500)]
efi: widen operand to avoid overflow

CID #1287141.

6 years agocore: issue error on oom we can do nothing about
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:10:06 +0000 (21:10 -0500)]
core: issue error on oom we can do nothing about

CID #1287142.

6 years agoµhttp-util: setup gnutls logs in one function
Zbigniew Jędrzejewski-Szmek [Sat, 14 Mar 2015 02:07:45 +0000 (21:07 -0500)]
µhttp-util: setup gnutls logs in one function

6 years agoudev: make set_usec_initialized() internal to libudev
Tom Gundersen [Fri, 13 Mar 2015 17:43:00 +0000 (18:43 +0100)]
udev: make set_usec_initialized() internal to libudev

Instead introduce ensure_usec_initialized(), which copies the timestamp if possible otherwise
sets it to now(CLOCK_MONOTONIC).

6 years agosd-rtnl: read_message - don't set group if not needed
Tom Gundersen [Fri, 13 Mar 2015 15:15:03 +0000 (16:15 +0100)]
sd-rtnl: read_message - don't set group if not needed

6 years agosd-rtnl: process - only apply matches to broadcast messages
Tom Gundersen [Fri, 13 Mar 2015 15:13:24 +0000 (16:13 +0100)]
sd-rtnl: process - only apply matches to broadcast messages

6 years agosd-rtnl: improve detection of broadcast messages
Tom Gundersen [Fri, 13 Mar 2015 15:12:57 +0000 (16:12 +0100)]
sd-rtnl: improve detection of broadcast messages

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

6 years agosd-rtnl: never set serial to 0
Tom Gundersen [Fri, 13 Mar 2015 14:49:07 +0000 (15:49 +0100)]
sd-rtnl: never set serial to 0

In the unlikely event that we wrap the counter, skip 0 as this is used
for broadcasts.

Suggested by Richard Maw.

6 years agotree-wide: there is no ENOTSUP on linux
David Herrmann [Fri, 13 Mar 2015 13:08:00 +0000 (14:08 +0100)]
tree-wide: there is no ENOTSUP on linux

Replace ENOTSUP by EOPNOTSUPP as this is what linux actually uses.

6 years agobus: stop using EDEADLOCK
David Herrmann [Fri, 13 Mar 2015 12:55:54 +0000 (13:55 +0100)]
bus: stop using EDEADLOCK

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.

6 years agojournal-remote: stop using EWOULDBLOCK
David Herrmann [Fri, 13 Mar 2015 12:51:55 +0000 (13:51 +0100)]
journal-remote: stop using EWOULDBLOCK

There is no reason to ever use EWOULDBLOCK. It's equivalent to EAGAIN on
all architectures on linux.

6 years agoudev: dont use EWOULDBLOCK
David Herrmann [Fri, 13 Mar 2015 12:41:55 +0000 (13:41 +0100)]
udev: dont use EWOULDBLOCK

EWOULDBLOCK is the same as EAGAIN, stop using it.

6 years agogpt-auto-generator: fix detection of /srv
Mathieu Chevrier [Fri, 13 Mar 2015 04:33:44 +0000 (00:33 -0400)]
gpt-auto-generator: fix detection of /srv

6 years agoman: update example 2 in
Zbigniew Jędrzejewski-Szmek [Fri, 13 Mar 2015 04:25:31 +0000 (00:25 -0400)]
man: update example 2 in

none/both/v4/v6 are deprecated in favour of no/yes/ipv4/ipv6.

6 years agopo: add Spanish translation
Alex Puchades [Fri, 13 Mar 2015 04:17:04 +0000 (00:17 -0400)]
po: add Spanish translation

6 years agosd-event: fix typo
Zbigniew Jędrzejewski-Szmek [Fri, 13 Mar 2015 04:03:41 +0000 (00:03 -0400)]
sd-event: fix typo

6 years agojournal-remote: process events without delay
Zbigniew Jędrzejewski-Szmek [Fri, 13 Mar 2015 04:02:28 +0000 (00:02 -0400)]
journal-remote: process events without delay

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.

6 years agojournal-remote: check also for EWOULDBLOCK
Zbigniew Jędrzejewski-Szmek [Fri, 13 Mar 2015 01:54:14 +0000 (21:54 -0400)]
journal-remote: check also for EWOULDBLOCK

This matches similar code elsewhere.

6 years agojournal-remote: downgrade routine messages to debug
Zbigniew Jędrzejewski-Szmek [Fri, 13 Mar 2015 01:29:28 +0000 (21:29 -0400)]
journal-remote: downgrade routine messages to debug

6 years agosd-pppoe: workaround for incomplete include in old kernels
Zbigniew Jędrzejewski-Szmek [Fri, 13 Mar 2015 00:50:08 +0000 (20:50 -0400)]
sd-pppoe: workaround for incomplete include in old kernels

6 years agonetworkd: Begin with serial number 1 for netlink requests
Richard Maw [Thu, 12 Mar 2015 18:14:58 +0000 (18:14 +0000)]
networkd: Begin with serial number 1 for netlink requests

"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.


[tomegun: sequence -> serial]

6 years agohwdb: update
Kay Sievers [Thu, 12 Mar 2015 17:34:23 +0000 (18:34 +0100)]
hwdb: update

6 years agobuild-sys: fix name of new rules file
Kay Sievers [Thu, 12 Mar 2015 16:44:58 +0000 (17:44 +0100)]
build-sys: fix name of new rules file

6 years agorules: merge tty and serial rules file
Kay Sievers [Thu, 12 Mar 2015 16:15:15 +0000 (17:15 +0100)]
rules: merge tty and serial rules file

6 years agorules: merge udev-late.rules files
Kay Sievers [Thu, 12 Mar 2015 15:34:18 +0000 (16:34 +0100)]
rules: merge udev-late.rules files

6 years agorules: default - remove legacy agpgart
Kay Sievers [Thu, 12 Mar 2015 15:30:05 +0000 (16:30 +0100)]
rules: default - remove legacy agpgart

6 years agorules: systemd - remove legacy "ram" from block device blacklist
Kay Sievers [Thu, 12 Mar 2015 15:28:38 +0000 (16:28 +0100)]
rules: systemd - remove legacy "ram" from block device blacklist

6 years agorules: move block device rules to its own rules file
Kay Sievers [Thu, 12 Mar 2015 15:09:46 +0000 (16:09 +0100)]
rules: move block device rules to its own rules file

6 years agorules: storage - relace blacklist with explicit whitelist
Kay Sievers [Thu, 12 Mar 2015 14:03:30 +0000 (15:03 +0100)]
rules: storage - relace blacklist with explicit whitelist

Newly added kernel drivers repeatedly pass our blacklist and
cause trouble for the devices, because they do not expect to
be examined by udev's default rules which include blkid.

This turns the blacklist into a whitelist. Device type which
need support for additional symlinks need to be added to the
whitelist now.

Note, that the by-id, by-path symlinks are only intended for
hotpluggable devices. There is no reason for exotic, or for
statically configured devices to provide them.

6 years agoTODO
Tom Gundersen [Thu, 12 Mar 2015 12:03:44 +0000 (13:03 +0100)]

6 years agoman: split paragraph
David Herrmann [Thu, 12 Mar 2015 11:46:46 +0000 (12:46 +0100)]
man: split paragraph

Explicitly put the "multiple EnvironmentFile=" description into its own
paragraph to make it much easier to find.

6 years agocore: add missing words to my fix of explanation of associativity
Tom Gundersen [Thu, 12 Mar 2015 11:23:59 +0000 (12:23 +0100)]
core: add missing words to my fix of explanation of associativity

6 years agoudevd: improve handling of failed worker
Tom Gundersen [Wed, 11 Mar 2015 14:41:32 +0000 (15:41 +0100)]
udevd: improve handling of failed worker

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.