| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Follow-up for a41ff38b0999fb83464309a29b8f39450b8d4b85.
|
|
travis: build and run fuzzers against crash reproducers
|
|
This should prevent Travis CI from terminating build jobs
that don't print anything for more than 10 minutes.
See https://travis-ci.org/systemd/systemd/builds/451737177.
|
|
|
|
prefixlen when family == AF_INET6 (#10665)
Follow-up for a4798d4e6d88c2be2625ce62d8326eaa9b80f2ee.
Fixes #10662.
|
|
Otherwise `coverity.sh build` will fail with
```
find: '/var/tmp/coverity-scan-analysis': No such file or directory
```
See https://travis-ci.org/systemd/systemd/jobs/451683385.
|
|
another bios version for same model with portrait screen.
|
|
Fix & re-enable Travis CI
|
|
so that it will be possible to work on the test failure and try to make
Travis CI work at the same time.
|
|
Add a couple of fuzzers for network_load_one and netdev_load_one
|
|
dnf upgrade on Fedora Rawhide pulls in unwanted selinux-policy
packages which breaks the system in several ways (and usually
ends up with crashed systemd)
|
|
We currently don't have any upstream but it doesn't mean that
it should be impossible to experiment with local ones :-)
|
|
This should help the fuzzers to discover code paths faster.
In case anyone is interested, they were generated with the following script
```
perl -aF'/[\s,]+/' -ne '
if (my ($s, $d) = ($F[0] =~ /^([^\s\.]+)\.([^\s\.]+)$/)) { $d{$s}{$d} = 1; }
END { while (my ($key, $value) = each %d) {
printf "[%s]\n%s\n", $key, join("\n", keys(%$value))
}}'
```
by passing src/network/networkd-network-gperf.gperf and
src/network/netdev/netdev-gperf.gperf to it.
|
|
This is a follow-up to https://github.com/systemd/systemd/pull/10653.
|
|
|
|
|
|
|
|
|
|
|
|
The assertion was added in dbffab87f1504abc9f but I'm not exactly sure
why. Now it just crashes a fuzzer I wrote. I, of course, could fix the fuzzer
so that it would generate names ending in ".network" if anyone would tell
me why the assertion should be kept here.
|
|
This gets around https://github.com/google/sanitizers/issues/992.
|
|
random-util.c mini-fixes
|
|
Currently we consider any framebuffer device as enough to have a
valid graphical session, but this might lead to many false postives
like in the case of framebuffer devices that have a linked drm card
which is still in the process of being added, or for vesa fb, and
so it doesn't ensure us that we can have a proper graphical session.
Since these days we normally don't consider anything without a DRM
card able to provide a full graphical session, let's not set this
at this level.
Drivers which can provide a graphical session with the sole fb are
still free to mark any device as `master-of-seat`
Fixes #10435
|
|
udev: improve performance
|
|
update log messages
|
|
Another solution to fix wireguard issues
|
|
This also changes the rational number treatment.
So, the limitations introduced by 8079c90333422bbc008b68a9b7cefbdb8a15a4e9
and f6a178e91dd5fccf43f659eca887788fd5dcdccf are relaxed.
Fixes #10619.
|
|
|
|
|
|
The uevent handling in udevd is not cpu hungry.
So, let's increase the default number of workers per cpu.
This decrease the number of queued uevents.
Without this commit (children_max is 16 on my laptop)
```
$ journalctl -b -u systemd-udevd.service | grep reached | wc -l
1544
```
With this commit (children_max is 30 on my laptop)
```
$ journalctl -b -u systemd-udevd.service | grep reached | wc -l
7
```
|
|
During boot process, many worker processes are forked and killed.
To decrease cycles of forking and killing worker, let's wait
3 seconds before killing workers. If new uevent or inotify event
comes within the delay, the killing porcess will be cancelled.
|
|
This should make debugging somewhat easier
|
|
If there exists pending uevents, then sd-event invokes uevent handler.
So, it is not necessary to receive the next uevent in inotify event.
|
|
|
|
networkd: don't remove ip address or route
|
|
|
|
udevadm: use write_string_file() helper function
|
|
fixes: 53b1f7d
|
|
lldp,ndisc: update debug logs
|
|
sysctl is disabled for /proc mounted from an user namespace thus entries like
/proc/sys/net/unix/max_dgram_qlen do not exist. In this case, skip the error
and do not try to change the default for the AF_UNIX datagram queue length.
|
|
CID 1396557
|
|
In case networkd is restarted this prevents a removal of an already existing
route that would be configured using networkd. With the proposed changes the
route will be kept on the interface without removing. This happens only on
physical hosts or VMs since networkd handles interface configuration slightly
different in containers.
|
|
In case networkd is restarted this prevents a removal of an already existing IP
address that would be configured using networkd. With the proposed changes the
IP address will be kept on the interface without removing. This happens only on
physical hosts or VMs since networkd handles interface configuration slightly
different in containers.
|
|
|
|
and friends
|
|
under /proc or /sys
|
|
|
|
|
|
|
|
|
