Since fchmodat(2) on Linux doesn't support AT_SYMLINK_NOFOLLOW, we have to implement it using workarounds. There are two different ways, depending on whether the system supports O_PATH or not. In the case O_PATH is supported, we rely on the behavhior of openat(2) when passing O_NOFOLLOW | O_PATH and the file is a symbolic link. Even if openat_file() already adds O_NOFOLLOW to the flags, this patch makes it explicit that we need both creation flags to obtain the expected behavior. This is only cleanup, no functional change. Signed-off-by: Greg Kurz <groug@kaod.org> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org> |
||
---|---|---|
.. | ||
9p-handle.c | ||
9p-local.c | ||
9p-local.h | ||
9p-posix-acl.c | ||
9p-proxy.c | ||
9p-proxy.h | ||
9p-synth.c | ||
9p-synth.h | ||
9p-util.c | ||
9p-util.h | ||
9p-xattr-user.c | ||
9p-xattr.c | ||
9p-xattr.h | ||
9p.c | ||
9p.h | ||
codir.c | ||
cofile.c | ||
cofs.c | ||
coth.c | ||
coth.h | ||
coxattr.c | ||
Makefile.objs | ||
trace-events | ||
virtio-9p-device.c | ||
virtio-9p.h | ||
xen-9p-backend.c | ||
xen-9pfs.h |