diff options
author | Aleksa Sarai <cyphar@cyphar.com> | 2023-07-28 14:58:26 +0300 |
---|---|---|
committer | Christian Brauner <brauner@kernel.org> | 2023-07-28 17:43:05 +0300 |
commit | 5daeb41a6fc9d0d81cb2291884b7410e062d8fa1 (patch) | |
tree | d78ff44ccaee481643db3dc9e290db4a69b905c7 /arch/sparc | |
parent | 4859c257d295949c23f4074850a8c2ec31357abb (diff) | |
download | linux-5daeb41a6fc9d0d81cb2291884b7410e062d8fa1.tar.xz |
fchmodat2: add support for AT_EMPTY_PATH
This allows userspace to avoid going through /proc/self/fd when dealing
with all types of file descriptors for chmod(), and makes fchmodat2() a
proper superset of all other chmod syscalls.
The primary difference between fchmodat2(AT_EMPTY_PATH) and fchmod() is
that fchmod() doesn't operate on O_PATH file descriptors by design. To
quote open(2):
> O_PATH (since Linux 2.6.39)
> [...]
> The file itself is not opened, and other file operations (e.g.,
> read(2), write(2), fchmod(2), fchown(2), fgetxattr(2), ioctl(2),
> mmap(2)) fail with the error EBADF.
However, procfs has allowed userspace to do this operation ever since
the introduction of O_PATH through magic-links, so adding this feature
is only an improvement for programs that have to mess around with
/proc/self/fd/$n today to get this behaviour. In addition,
fchownat(AT_EMPTY_PATH) has existed since the introduction of O_PATH and
allows chown() operations directly on O_PATH descriptors.
Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
Acked-by: Alexey Gladkov <legion@kernel.org>
Message-Id: <20230728-fchmodat2-at_empty_path-v1-1-f3add31d3516@cyphar.com>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'arch/sparc')
0 files changed, 0 insertions, 0 deletions