Lines Matching refs:ownership

7 reading from or writing ownership to disk, reporting ownership to userspace, or
171 When a process creates or wants to change ownership of a file, or when the
172 ownership of a file is read from disk by a filesystem, the userspace id is
199 example, it is used when reporting back the ownership of a file to userspace
239 ownership information about the file the kernel can't simply map the id back up
345 but they are exclusively used when determining file ownership which is why they
478 In order to report ownership to userspace the kernel uses the crossmapping
492 idmapping. Thus, the kernel will report the ownership of this file as the
504 In order to report ownership to userspace the kernel uses the crossmapping
518 idmapping. Thus, the kernel will report the ownership of this file as the
558 Of course the administrator has the option to recursively change ownership via
559 ``chown()``. For example, they could change ownership so that ``dir`` and all
561 idmapping. Let's assume they change ownership so it is compatible with the
581 In both cases changing ownership recursively has grave implications. The most
582 obvious one is that ownership is changed globally and permanently. In the home
583 directory case this change in ownership would even need to happen everytime the
588 inside user namespaces. But this would also change ownership globally and the
589 change in ownership is tied to the lifetime of the filesystem mount, i.e. the
590 superblock. The only way to change ownership is to completely unmount the
601 They allow to expose the same set of dentries with different ownership at
607 Idmapped mounts make it possible to change ownership in a temporary and
608 localized way. The ownership changes are restricted to a specific mount and the
609 ownership changes are tied to the lifetime of the mount. All other users and
662 When the caller queries the ownership of this file via ``stat()`` the kernel
747 So the ownership that lands on disk will be ``u1000``.
780 So the ownership that lands on disk will be ``u1000``.
792 In order to report ownership to userspace the kernel now does three steps using
828 Again, in order to report ownership to userspace the kernel now does three
854 Changing ownership on a home directory
871 idmapping which means users on the host can change the ownership of directories
885 depending on what ownership they would prefer to end up on the portable storage
920 Now let's briefly look at what ownership the caller with id ``u1125`` will see