| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
fuzz: fix oss-fuzz#8658
|
| | |
|
|\ \
| |/
|/| |
Fixes oss-fuzz#11344
|
| | |
|
|\ \
| | |
| | | |
networkd: add 6rd support for sit netdevs
|
| | |
| | |
| | |
| | |
| | |
| | | |
Unfortunately we can't check the 6rd attribute, because it's not
exposed in /sys or anywhere other than netlink... But at least we
can check that networkd brings up an interface that looks right.
|
| | | |
|
|\ \ \
| | | |
| | | | |
udev-test: remove a check for whether the test is run in a container
|
| | | |
| | | |
| | | |
| | | | |
This is basically a replacement for 0eb3cc88504b5d8f74.
|
| | | |
| | | |
| | | |
| | | | |
It's too broad a check that prevents the test from running on Travis CI.
|
| | | | |
|
| |_|/
|/| | |
|
| | | |
|
| |/
|/| |
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
This adds testcases of oss-fuzz#11286, oss-fuzz#11287, oss-fuzz#11296,
oss-fuzz#11297, and oss-fuzz#11299.
The issue was fixed by 62facba19ad645df7fb425ce170bdbda208b303c.
|
| |
|
|
|
|
| |
Follow-up for a41ff38b0999fb83464309a29b8f39450b8d4b85.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
fixes: 53b1f7d
|
|\
| |
| | |
test: mask hwdb-update.services in most tests
|
| | |
|
| |
| |
| |
| | |
This may make CIs run faster.
|
| |
| |
| |
| |
| | |
As the test randomly fails with timeout.
This may fix #10274.
|
|\ \
| | |
| | | |
network: fix several issues in config parser
|
| | | |
|
| |/
| |
| |
| |
| |
| | |
After ec6a47044a2ab321ae6427ce0d9fa3f6a17544a8, networkd starts
soon after removing links used by previous test. That causes
some racy situation of removing links and detecting links by networkd.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It's not entirely impossible to screw something up playing with
kernel modules on a Saturday evening :-) This PR fixes a scenario
where a module has been loaded into the kernel but the module itself
has been removed from the disk.
```
$ lsmod | grep wireg
wireguard 225280 0
ip6_udp_tunnel 16384 1 wireguard
udp_tunnel 16384 1 wireguard
$ modprobe wireguard
modprobe: FATAL: Module wireguard not found in directory /lib/modules/4.18.16-200.fc28.x86_64
$ sudo ./systemd-networkd-tests.py NetworkdNetDevTests.test_wireguard
...
modprobe: FATAL: Module wireguard not found in directory /lib/modules/4.18.16-200.fc28.x86_64
test_wireguard (__main__.NetworkdNetDevTests) ... unexpected success
----------------------------------------------------------------------
Ran 1 test in 5.152s
FAILED (unexpected successes=1)
```
This is a follow-up to https://github.com/systemd/systemd/pull/10625.
|
|/ |
|
|
|
|
|
|
| |
aren't available
Closes https://github.com/systemd/systemd/issues/10617.
|
|
|
|
|
| |
Depending on the content of /etc/iproute2/rt_dsfield, ip can print either
`0x08` or `throughput` as was shown in https://github.com/systemd/systemd/issues/10617#issuecomment-435200859.
|
|
|
|
|
|
|
|
|
| |
Add support for bonding options system prio, port key and actor system mac.
These options exist in the linux kernel since 4.2
(torvalds/linux@171a42c38c6e1)
Details:
https://www.kernel.org/doc/Documentation/networking/bonding.txt
|
|
|
|
|
|
|
|
|
| |
I went through my antique collection of fuzzers the other day
to see which ones I hadn't sent upstream yet. This one
seems to be nice to have and ready to be merged. As far as I can
tell, it hasn't managed to find anything useful yet,
but it's better to be safe than sorry especially when it comes to networking
code :-)
|
|\
| |
| | |
json: a comprehensive fix for oss-fuzz#10908
|
| |
| |
| |
| | |
https://oss-fuzz.com/download?testcase_id=5639441482252288
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
(#10486)
The latter is merely a compat symlink nowadays.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, if I run the full "run-integration-tests.sh" script it will
fail on my machine because it fills up /var/tmp whith just too much
crap until the disk is full.
Let's make sure that "run-integration-tests.sh" cleans up after every
test. For that change the make targets to run from "clean setup run" to
"clean setup run clean" — except that that doesn't work since make is
smart enough to realize that the same target appears twice on the
command line and will only execute it once. Let's fix that by defining
another target "clean-again" which is just like "clean", but allows us
to be added to the same command line a second time. Then, let's build
with "clean setup run clean-again" and all is good.
While we are at it, let's also add .PHONY where appropriate, after all
these all are phony targets.
|
|
|
|
|
|
|
|
|
| |
Add LogRateLimitIntervalSec= and LogRateLimitBurst= options for
services. If provided, these values get passed to the journald
client context, and those values are used in the rate limiting
function in the journal over the the journald.conf values.
Part of #10230
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default, UBSan neither crashes nor exits with a non-zero exit code
when undefined behavior has been detected. This is problematic because
it makes it much harder to catch issues like https://github.com/systemd/systemd/issues/10346,
https://github.com/systemd/systemd/issues/10347, and https://github.com/systemd/systemd/issues/10333.
In fact, those issue were found just because I decided to grep
the test log, which isn't something that I normally do :-)
As it turns out, the only way to make UBSan signal that something is wrong that works more or less
reliably everywhere is to pass halt_on_error=1 (though, it's probably worth noting that it's currently
not set for PID1 in order not to trigger kernel panics).
See https://reviews.llvm.org/D35085#804183 and https://chromium.googlesource.com/chromium/src/testing/libfuzzer/+/HEAD/reference.md
|