| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Valid boolean values for meson are 'true' and 'false',
not 'yes' and 'no'.
|
| | |
|
| |
|
|
| |
As a follow-up from #11427.
|
| |
|
|
| |
Closes #11479.
|
| |\
| |
| | |
Make udev link re-renaming conditional
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, this system call was included in @system-service since it is
a "getter" only, i.e. only queries information, and doesn't change
anything, and hence was considered not risky.
However, as it turns out, mincore() is actually security sensitive, see
the discussion here:
https://lwn.net/Articles/776034/
Hence, let's adjust the system call filter and drop mincore() from it.
This constitues a compatibility break to some level, however I presume
we can get away with this as the systemcall is pretty exotic. The fact
that it is pretty exotic is also reflected by the fact that the kernel
intends to majorly change behaviour of the system call soon (see the
linked LWN article)
|
| |/
|
|
|
|
| |
These sysctls were added in Linux 4.19 (torvalds/linux@30aba6656f), and
we should enable them just like we enable the older hardlink/symlink
protection since v199. Implements #11414.
|
| | |
|
| | |
|
| |
|
|
| |
https://github.com/systemd/systemd/pull/10802#issuecomment-453772058
|
| | |
|
| |
|
|
|
|
| |
Follow-up for aa2437e2aee003a361debbb34b341931caf49b3b.
Closes #11329.
|
| |
|
|
|
|
|
|
|
|
| |
Nitpicky, but we've used a lot of random spacings and names in the past,
but we're trying to be completely consistent on "cgroup vN" now.
Generated by `fd -0 | xargs -0 -n1 sed -ri --follow-symlinks 's/cgroups? ?v?([0-9])/cgroup v\1/gI'`.
I manually ignored places where it's not appropriate to replace (eg.
"cgroup2" fstype and in src/shared/linux).
|
| | |
|
| |\
| |
| | |
NEWS and build system bump for 240
|
| | | |
|
| |\ \
| | |
| | | |
cgroup: Imply systemd.unified_cgroup_hierarchy=1 on cgroup_no_v1=all
|
| | | | |
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit edda44605f06a41fb86b7ab8128dcf99161d2344.
The kernel explicitly supports resuming with a different kernel than the one
used before hibernation. If this is something that shouldn't be supported, the
place to change this is in the kernel. We shouldn't censor something that this
exclusively in the kernel's domain.
People might be using this to switch kernels without restaring programs, and
we'd break this functionality for them.
Also, even if resuming with a different kernel was a bad idea, we don't really
prevent that with this check, since most users have more than one kernel and
can freely pick a different one from the menu. So this only affected the corner
case where the kernel has been removed, but there is no reason to single it
out.
|
| |/
|
|
| |
Which was disabled by #10117.
|
| |
|
|
|
|
| |
This ain't so easy to express without using too much technical language...
https://github.com/systemd/systemd/pull/10094#issuecomment-427407570
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Which was added by #11142.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From WordNet (r) 3.0 (2006) [wn]:
time-out
n 1: a brief suspension of play; "each team has two time-outs left"
From The Free On-line Dictionary of Computing (18 March 2015) [foldoc]:
timeout
A period of time after which an error condition is raised if
some event has not occured. A common example is sending a
message. If the receiver does not acknowledge the message
within some preset timeout period, a transmission error is
assumed to have occured.
|
| | |
|
| |
|
|
| |
Needs lots of updates still, but let's get the party started.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
We now settled on 512K, and forgot to update NEWS.
Moreover, explain why 512K was chosen.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This switches the RFC3704 Reverse Path filtering from Strict mode to Loose
mode. The Strict mode breaks some pretty common and reasonable use cases,
such as keeping connections via one default route alive after another one
appears (e.g. plugging an Ethernet cable when connected via Wi-Fi).
The strict filter also makes it impossible for NetworkManager to do
connectivity check on a newly arriving default route (it starts with a
higher metric and is bumped lower if there's connectivity).
Kernel's default is 0 (no filter), but a Loose filter is good enough. The
few use cases where a Strict mode could make sense can easily override
this.
The distributions that don't care about the client use cases and prefer a
strict filter could just ship a custom configuration in
/usr/lib/sysctl.d/ to override this.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
After discussions with kernel folks, a system with memcg really
shouldn't need extra hard limits on file descriptors anymore, as they
are properly accounted for by memcg anyway. Hence, let's bump these
values to their maximums.
This also adds a build time option to turn thiss off, to cover those
users who do not want to use memcg.
|
| | |
|
| |\
| |
| | |
Test reporting improvements
|
| | | |
|
| |/
|
|
| |
https://github.com/systemd/systemd/blob/master/docs/* to point to proper documentation
|
| |\
| |
| | |
some nss deadlock love
|
| | | |
|
| |/
|
|
| |
default to it in 241
|
| |
|
|
|
|
|
|
|
|
|
| |
Back in 2012 the project was renamed, see the release notes for v 0.105
[https://cgit.freedesktop.org/polkit/tree/NEWS#n754]. Let's update our
documentation and comments to do the same. Referring to PolicyKit is confusing
to users because at the time the polkit api changed too, and we support the new
version. I updated NEWS too, since all the references to PolicyKit there were
added after the rename.
"PolicyKit" is unchanged in various URLs and method call names.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Follow-up for be405b909e5d78b43e3af47e0d10cd84c714e2f3.
|
