~lukeshu/systemd - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2016-12-17	Modify mount_propagation_flags_from_string to return a normal int code	Zbigniew Jędrzejewski-Szmek
	This means that callers can distiguish an error from flags==0, and don't have to special-case the empty string.
2016-12-13	core: hook up MountFlags= to the transient unit logic	Lennart Poettering
	This makes "systemd-run -p MountFlags=shared -t /bin/sh" work, by making MountFlags= to the list of properties that may be accessed transiently.
2016-12-01	tree-wide: stop using canonicalize_file_name(), use chase_symlinks() instead	Lennart Poettering
	Let's use chase_symlinks() everywhere, and stop using GNU canonicalize_file_name() everywhere. For most cases this should not change behaviour, however increase exposure of our function to get better tested. Most importantly in a few cases (most notably nspawn) it can take the correct root directory into account when chasing symlinks.
2016-10-11	nspawn,mount-util: add [u]mount_verbose and use it in nspawn	Zbigniew Jędrzejewski-Szmek
	This makes it easier to debug failed nspawn invocations: Mounting sysfs on /var/lib/machines/fedora-rawhide/sys (MS_RDONLY\|MS_NOSUID\|MS_NOEXEC\|MS_NODEV "")... Mounting tmpfs on /var/lib/machines/fedora-rawhide/dev (MS_NOSUID\|MS_STRICTATIME "mode=755,uid=1450901504,gid=1450901504")... Mounting tmpfs on /var/lib/machines/fedora-rawhide/dev/shm (MS_NOSUID\|MS_NODEV\|MS_STRICTATIME "mode=1777,uid=1450901504,gid=1450901504")... Mounting tmpfs on /var/lib/machines/fedora-rawhide/run (MS_NOSUID\|MS_NODEV\|MS_STRICTATIME "mode=755,uid=1450901504,gid=1450901504")... Bind-mounting /sys/fs/selinux on /var/lib/machines/fedora-rawhide/sys/fs/selinux (MS_BIND "")... Remounting /var/lib/machines/fedora-rawhide/sys/fs/selinux (MS_RDONLY\|MS_NOSUID\|MS_NOEXEC\|MS_NODEV\|MS_BIND\|MS_REMOUNT "")... Mounting proc on /proc (MS_NOSUID\|MS_NOEXEC\|MS_NODEV "")... Bind-mounting /proc/sys on /proc/sys (MS_BIND "")... Remounting /proc/sys (MS_RDONLY\|MS_NOSUID\|MS_NOEXEC\|MS_NODEV\|MS_BIND\|MS_REMOUNT "")... Bind-mounting /proc/sysrq-trigger on /proc/sysrq-trigger (MS_BIND "")... Remounting /proc/sysrq-trigger (MS_RDONLY\|MS_NOSUID\|MS_NOEXEC\|MS_NODEV\|MS_BIND\|MS_REMOUNT "")... Mounting tmpfs on /tmp (MS_STRICTATIME "mode=1777,uid=0,gid=0")... Mounting tmpfs on /sys/fs/cgroup (MS_NOSUID\|MS_NOEXEC\|MS_NODEV\|MS_STRICTATIME "mode=755,uid=0,gid=0")... Mounting cgroup on /sys/fs/cgroup/systemd (MS_NOSUID\|MS_NOEXEC\|MS_NODEV "none,name=systemd,xattr")... Failed to mount cgroup on /sys/fs/cgroup/systemd (MS_NOSUID\|MS_NOEXEC\|MS_NODEV "none,name=systemd,xattr"): No such file or directory
2016-09-25	namespace: rework how ReadWritePaths= is applied	Lennart Poettering
	Previously, if ReadWritePaths= was nested inside a ReadOnlyPaths= specification, then we'd first recursively apply the ReadOnlyPaths= paths, and make everything below read-only, only in order to then flip the read-only bit again for the subdirs listed in ReadWritePaths= below it. This is not only ugly (as for the dirs in question we first turn on the RO bit, only to turn it off again immediately after), but also problematic in containers, where a container manager might have marked a set of dirs read-only and this code will undo this is ReadWritePaths= is set for any. With this patch behaviour in this regard is altered: ReadOnlyPaths= will not be applied to the children listed in ReadWritePaths= in the first place, so that we do not need to turn off the RO bit for those after all. This means that ReadWritePaths=/ReadOnlyPaths= may only be used to turn on the RO bit, but never to turn it off again. Or to say this differently: if some dirs are marked read-only via some external tool, then ReadWritePaths= will not undo it. This is not only the safer option, but also more in-line with what the man page currently claims: "Entries (files or directories) listed in ReadWritePaths= are accessible from within the namespace with the same access rights as from outside." To implement this change bind_remount_recursive() gained a new "blacklist" string list parameter, which when passed may contain subdirs that shall be excluded from the read-only mounting. A number of functions are updated to add more debug logging to make this more digestable.
2016-07-19	namespace: unify limit behavior on non-directory paths	Alessandro Puccetti
	Despite the name, `Read{Write,Only}Directories=` already allows for regular file paths to be masked. This commit adds the same behavior to `InaccessibleDirectories=` and makes it explicit in the doc. This patch introduces `/run/systemd/inaccessible/{reg,dir,chr,blk,fifo,sock}` {dile,device}nodes and mounts on the appropriate one the paths specified in `InacessibleDirectories=`. Based on Luca's patch from https://github.com/systemd/systemd/pull/3327
2016-02-10	tree-wide: remove Emacs lines from all files	Daniel Mack
	This should be handled fine now by .dir-locals.el, so need to carry that stuff in every file.
2015-12-01	basic: re-sort includes	Thomas Hindoe Paaboel Andersen
	My previous patch to only include what we use accidentially placed the added inlcudes in non-sorted order.
2015-11-30	basic: include only what we use	Thomas Hindoe Paaboel Andersen
	This is a cleaned up result of running iwyu but without forward declarations on src/basic.
2015-10-27	automount: move generically userful call repeat_mount() into mount-util.[ch]	Lennart Poettering

2015-10-27	mount-util: move fstype_is_network() and name_to_handle_at() definitions over	Lennart Poettering

2015-10-27	util-lib: move mount related utility calls to mount-util.[ch]	Lennart Poettering