summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* hwdb: add Medion Akoya E2228T MD61900 (#18317)mastercorvusnix2021-01-211-0/+4
| | | | Add a model-specific entry for Medion Akoya E2228T MD61900 accelerometer to 60-sensor.hwdb so the orientation is detected correctly.
* Merge pull request #18327 from benzea/benzea/libfprint-autosuspend-hwdbZbigniew Jędrzejewski-Szmek2021-01-213-2/+279
|\ | | | | Pull libfprint autosuspend hwdb
| * hwdb: Pull autosuspend rules from upstream libfprintBenjamin Berg2021-01-203-1/+278
| | | | | | | | | | | | | | | | | | libfprint includes a list of known fingerprint readers that can be autosuspended. Upstream libfprint generates this file from the USB IDs registered to drivers and a list of well-known readers that are currently unsupported. Closes: #17663
| * tools: Pass source directory to autosuspend-update.shBenjamin Berg2021-01-192-2/+2
| | | | | | | | | | This makes sense so that we can extend the script to also update other files.
* | Merge pull request #18329 from poettering/notify-chrootYu Watanabe2021-01-2112-12/+40
|\ \ | | | | | | chroot/sd_notify() fixes
| * | portabled: update profiles to current semanticsLennart Poettering2021-01-204-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | MountAPIVFS= implicitly mounts /run as tmpfs now, no need to do this explicitly. The notification socket is now implicitly mounted too, if NotifyAccess= and RootImage=/RootDirectory= are used together.
| * | man: document how get logging to work in a RootDirectory=/RootImage= environmentLennart Poettering2021-01-201-0/+14
| | | | | | | | | | | | Fixes: #18051
| * | core: make NotifyAccess= in combination with RootDirectory=/RootImage= workLennart Poettering2021-01-207-5/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously if people enabled RootDirectory=/RootImage= and NotifyAccess= together, things wouldn't work, they'd have to explicitly add BindReadOnlyPaths=/run/systemd/notify too. Let's make this implicit. Since both options are opt-in, if people use them together it would be pointless not also defining the BindReadOnlyPaths= entry, in which case we can just do it automatically. See: #18051
* | | varlink: make 'userdata' pointer inheritance from varlink server to ↵Lennart Poettering2021-01-217-11/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | connection optional @keszybz's right on https://github.com/systemd/systemd/pull/18248#issuecomment-760798473: swapping out the userdata pointer of a live varlink connection is iffy. Let's fix this by making the userdata inheritance from VarlinkServer object to the Varlink connection object optional: we want it for most cases, but not all, i.e. all those cases where the calls implemented as varlink methods are stateless and can be answered synchronously. For the other cases (i.e. where we want per-connection objects that wrap the asynchronous operation as it goes on) let's not do such inheritance but initialize the userdata pointer only once we have it. THis means the original manager object must be manually retrieved from the VarlinkServer object, which in turn needs to be requested from the Varlink connection object. The userdata inheritance is now controlled by the VARLINK_INHERIT_USERDATA flag passed at VarlinkServer construction. Alternative-to: #18248
* | | Merge pull request #18311 from poettering/sysext-fixupsYu Watanabe2021-01-213-234/+276
|\ \ \ | |/ / |/| | sysext: post-merge fixups
| * | man: document recent systemd-sysext interface changesLennart Poettering2021-01-201-16/+26
| | |
| * | sysext: add --force swich for forcibly ignoring version incompatibilitiesLennart Poettering2021-01-201-0/+13
| | |
| * | sysext: rework command line interface to be verb-basedLennart Poettering2021-01-202-166/+163
| | | | | | | | | | | | | | | | | | As suggested by @yuwata: https://github.com/systemd/systemd/pull/18181#pullrequestreview-570826113
| * | sysext: split version validation logic into function of its ownLennart Poettering2021-01-201-49/+73
| | | | | | | | | | | | Just some simple refactoring to simplify the logic.
| * | sysext: use log_setup_cli()Lennart Poettering2021-01-201-3/+1
| | |
* | | Merge pull request #18325 from ssahani/more-cleanupLuca Boccassi2021-01-2010-71/+37
|\ \ \ | | | | | | | | Tree wide various cleanup
| * | | btrfs-util: tighten variable scope used in loopSusant Sahani2021-01-201-17/+12
| | | |
| * | | analyze: tighten variable scope used in loopSusant Sahani2021-01-201-4/+2
| | | |
| * | | sd-event: Use hashmap_ensure_putSusant Sahani2021-01-201-5/+1
| | | |
| * | | sd-event: Use hashmap_ensure_putSusant Sahani2021-01-201-5/+1
| | | |
| * | | sd-device: Use TAKE_PTRSusant Sahani2021-01-201-1/+3
| | | |
| * | | sd-device: Use hashmap_ensure_putSusant Sahani2021-01-201-5/+1
| | | |
| * | | udev-rules: use ordered_hashmap_ensure_putSusant Sahani2021-01-201-6/+4
| | | |
| * | | network: networkd-network use TAKE_PTRSusant Sahani2021-01-201-1/+1
| | | |
| * | | network: Use hashmap_ensure_putSusant Sahani2021-01-201-4/+2
| | | |
| * | | network: ndisc - Use ordered_set_ensure_putSusant Sahani2021-01-201-4/+2
| | | |
| * | | machine: Use hashmap_ensure_putSusant Sahani2021-01-201-5/+1
| | | |
| * | | logind: Use hashmap_ensure_putSusant Sahani2021-01-201-5/+4
| | | |
| * | | journal: Use cleanup_freeSusant Sahani2021-01-201-5/+3
| | | |
| * | | Journal: Use hashmap_ensure_putSusant Sahani2021-01-201-5/+1
| | | |
* | | | udev/cdrom_id: re-enable logging related functionsYu Watanabe2021-01-201-0/+5
| |/ / |/| | | | | | | | | | | | | | The logging related functions are mistakenly located in main() by a084b3878955bc1b93adcaa7a41acb83b18eff9b, and dropped by 23afa884d4f3bcd97160a893816f9ba170f62ad4.
* | | path-util: simplify check_x_access()Yu Watanabe2021-01-201-23/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Follow-up for ece852c84592220c3d6bb5a055fd8b84ea097290. This addresses the following comments by the Lennart: --- hmm, so this now does two access() calls for the case where the fd is not requested, and opens things up for races (theoretically, …). now, the access() code path was in place for optimization, but if an optimization is less sexy than the original (and i think it is less sexy, since more than one syscall, and non-atomic), i think we shouldn't do the optimization. maybe we should just always use open(O_PATH) now, and then fstat() it to check if regular file, and then access_fd() it for checking if its executable.
* | | sysext: install in rootbindir, remove template from unitLuca Boccassi2021-01-203-4/+4
|/ / | | | | | | This reverts commit 71ad75f30641b90f9ca0088869f164d9d085430f.
* | udev: use DEFINE_MAIN_FUNCTION in cdrom_idDan Streetman2021-01-201-14/+2
| | | | | | | | | | | | | | | | This was failing s390x ubuntu ci due to an old version of binutils; the binutils package in use for ubuntu ci tests has been updated and the build no longer fails, so this can use the macro again. Fixes: #18165
* | tree-wide: ignore messages with too long control dataLennart Poettering2021-01-203-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Apparently SELinux inserts control data into AF_UNIX datagrams where we don't expect it, thus miscalculating the control data. This looks like something to fix in SELinux, but we still should handle this gracefully and just drop the offending datagram and continue. recvmsg_safe() actually already drops the datagram, it's just a matter of actually ignoring EXFULL (which it generates if control data is too large) in the right places. This does this wherever an AF_UNIX/SOCK_DGRAM socket is used with recvmsg_safe() that is not just internal communication. Fixes: #17795 Follow-up for: 3691bcf3c5eebdcca5b4f1c51c745441c57a6cd1
* | Revert "test-functions: make sure we test our own libudev instead of the ↵Zbigniew Jędrzejewski-Szmek2021-01-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | host libudev" This reverts commit 73484ecff90f2cc235d827c0e955999bffe64dd0. 3976f372ae91e1cbe5ff9873aadfc2c43400452e moved libudev.so to be built in the main directory, so this addition to $LD_LIBRARY_PATH is now obsolete. After that commit, we build the following shared libraries: build/libnss_myhostname.so.2 build/libnss_mymachines.so.2 build/libnss_resolve.so.2 build/libnss_systemd.so.2 build/libsystemd.so.0.30.0 build/libudev.so.1.7.0 build/pam_systemd.so build/pam_systemd_home.so build/src/boot/efi/stub.so build/src/boot/efi/systemd_boot.so build/src/shared/libsystemd-shared-247.so EFI stubs don't matter, and libsystemd-shared-nnn.so is loaded through rpath, and is doesn't need to and shouldn't be in $LD_LIBRARY_PATH. In effect, we only ever need to add the main build directory to the search path.
* | markdown: fix commentLennart Poettering2021-01-191-1/+1
| | | | | | | | Follow-up for 2d816c9804c1d565797faff85c0fdbfb15f1e9d5
* | markdown: suggest backticks around uname -a outputLennart Poettering2021-01-191-1/+4
| | | | | | | | Fixes: #18238
* | execute: for processes where creds logic is turned off, don't pass creds ↵Lennart Poettering2021-01-191-1/+3
| | | | | | | | | | | | | | | | | | path to namespace logic Otherwise, the namespace logic will try to mount a dir that doesn't actually exist. Fixes: #18116
* | Merge pull request #18307 from poettering/import-verity-downloadLennart Poettering2021-01-1912-249/+524
|\ \ | | | | | | importd: when downloading raw image, also download .roothash.p7s and .verity along with it
| * | import: refactor how we do gpg validationLennart Poettering2021-01-194-67/+82
| | | | | | | | | | | | | | | Let's split out the actual gpg logic into a helper function, so that we can add alternative validations later on.
| * | import: optionally pull .verity + .roothash.p7s data when downloadingLennart Poettering2021-01-197-138/+254
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We already had support for downlading a .nspawn and a .roothash file, let's make the set complete, and also download .verity + roothash.p7s if it exists, as nspawn consumes that. Since there are now four kinds of additional resources to acquire, let's introduce a PullFlags flags value for this instead of separate 'bool' variables, it's just too many to always pass those around on the function parameter list.
| * | import: ignore non-successful HTTP codes for collecing image metadataLennart Poettering2021-01-191-1/+15
| | | | | | | | | | | | | | | | | | Previously we'd collect the data from redirects too, which wasn't particularly terrible, since these typically don't carry the data we were interested in, but it's still incorrect to do so.
| * | import: turn on HTTP logging in debug modeLennart Poettering2021-01-191-1/+2
| | |
| * | import: small memory management simplificationLennart Poettering2021-01-191-4/+2
| | |
| * | import: reset PullJob properlyLennart Poettering2021-01-191-0/+19
| | | | | | | | | | | | | | | | | | Properly reset all fields that have to do with the current GET job when we restart things. Previously we freed/reset only some stuff, leaking some memory even.
| * | import: rework how verification worksLennart Poettering2021-01-196-38/+133
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously the PullJob object took internal care of rerequested the SHA256SUMS file, if requesting <image>.sha256 didn't work. This was a weird a non-abstraction only used when actually getting the checksum files. Let's move this out of the PullJob, so that it is generic again, and does roughly the same stuff for all resources it is used for: let's define a generic .on_not_found() handler that can be set on a PullJob object, and is called whenever with see HTTP 404, and may be used to provide a new URL to try if the first didn't work. This is also preparation for later work to support PKCS#7 signatures instead of gpg signatures, where a similar logic is needed, and we thus should have a generic infrastructure place. This gets rid of the VerificationStyle field in the PullJob object: instead of storing this non-generic field we just derive the same information from the URL itself, which is safe, since we generated it ourselves earlier.
| * | import: use TAKE_PTR() where availableLennart Poettering2021-01-191-4/+2
| | |
| * | import: make scope of variable smallerLennart Poettering2021-01-191-1/+1
| | |
| * | import: comment indent fixLennart Poettering2021-01-191-1/+1
| | |
View Lorry Controller Status