| Age | Commit message (Collapse) | Author |
|---|
|
|
|
keymap: Add Samsung NP350V and NP670Z
|
|
typo
keymap: Add Samsung NP350V and NP670Z
|
|
utezduyar/feat/dump-sync-dbus-message-with-logging-on
sd-bus: dump sync messages in debug mode
|
|
build-sys: turn some warnings into errors
|
|
Make the build sys error out on missing function prototypes, missing
variable declarations, implicit function declarations or forgotten return
statements.
None of these conditions are acceptable, and by making them hard errors, the
build bots can detect them earlier.
|
|
Hwdb updates
|
|
|
|
Since 3.19, the devices have the proper vid/pid and the model number in the
name.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
|
|
mask/handlers
Also, when the child is potentially long-running make sure to set a
death signal.
Also, ignore the result of the reset operations explicitly by casting
them to (void).
|
|
|
|
core: log oom during killing spree
|
|
but don't do anything else. We still want to kill as much as
possible.
Coverity CID#996306
|
|
path-util: Fix path_is_mount_point for parent mount points in symlink mode
|
|
When we have a structure like this:
/bin -> /usr/bin
/usr is a mount point
Then path_is_mount_point("/bin", AT_SYMLINK_FOLLOW) needs to look at the pair
/usr/bin and /usr, not at the pair / and /usr/bin, as the latter have different
mount IDs. But we only want to consider the base name, not any parent.
Thus we have to resolve the given path first to get the real parent when
allowing symlinks.
Bug: https://github.com/systemd/systemd/issues/61
|
|
build-sys: always dist *.policy.in files
|
|
Unconditionally dist org.freedesktop.{import1,machine1}.policy.in, like all the
other *.policy.in files. This avoids missing policy files in the tarball.
Spotted by "make distcheck" failure with --disable-importd.
|
|
build-sys: don't suppress irrelevant warnings
|
|
Revert "hwdb: actually search /run/udev/hwdb.d"
|
|
|
|
util:bind_remount_recursive() fix "use after free" - 2
|
|
cryptsetup: craft a unique ID with the source device
|
|
sd-bus: add async convenience method call API
|
|
networkd: actually always use AddressFamilyBoolean as the bit mask it is
|
|
set_consume() does not return -EEXIST, but 0, in case the key is already
in the Set.
|
|
This reverts commit 46be6129d3e52556eb0f2ae4d07818f9f3f7af7a.
|
|
If cryptsetup is called with a source device as argv[3], then craft the
ID for the password agent with a unique device path.
If possible "/dev/block/<maj>:<min>" is used, otherwise the original
argv[3] is used.
This enables password agents like petera [1] to provide a password
according to the source device. The original ID did not carry enough
information and was more targeted for a human readable string, which
is specified in the "Message" field anyway.
With this patch the ID of the ask.XXX ini file looks like this:
ID=cryptsetup:/dev/block/<maj>:<min>
[1] https://github.com/npmccallum/petera
|
|
|
|
hwdb: actually search /run/udev/hwdb.d
|
|
rules: whitelist xvd* devices
|
|
DPI is guesswork, no specs found on the web and calculating DPIs on a
trackball is tedious.
|
|
The documentation claims hwdb entries may be placed in the volatile
/run/udev/hwdb.d directory but nothing actually looked at it.
|
|
Xen disks need to be whitelisted as well.
|
|
|
|
We do not trigger these warnings so no need to suppress them.
|
|
tree-wide: remove spurious space
|
|
Revert "networkd: create "kernel" setting for IPForwarding"
|
|
|
|
|
|
man: systemd.link - explain random MAC addresses
|
|
Two of the bits in the MAC address are set unconditioanlly, and the rest is randomized,
make this clear in the documentation (as it currently read as if it was all random).
|
|
kmod-setup: split warn flags
|
|
Traditionally, we used to warn about ipv6 being a module or being
unavailable. This was changed in b4aa82f16 ("kmod-setup: don't warn
when ipv6 can't be loaded") in a way that neither of the two conditions
will cause a log message.
Now, while running a setup without any IPv6 is completely fine and
shouldn't cause any warning, we should still warn about ipv6 being a
module instead of built-in.
To achieve this, split the boolean warn flag into two: one for a
feature not being built-in but shipped as a module, and one to
print an error when a module is entirely unavailable.
We will, however, still warn if kmod returns anything else than
-ENOENT in the attempt of loading the module, and at the very least,
turn the message into a debug log.
|
|
util:bind_remount_recursive() fix "use after free"
|
|
set_consume(done, x) consumes x with free(x)
but
mount(…, x, …) uses it afterwards.
coverity CID 1299006
|
|
README.md: add Coverity scan status badge
|
|
|
|
kmod-setup: don't warn when ipv6 can't be loaded (FDO bug #87475)
|
|
systemd-bootchart: Trivial typo fix in warning
|
