Add details on why AT_SYMLINK_NOFOLLOW is dangerous

The comment isn't helpful as-is. Provide some clarifying information.

Test: code compiles. No functional changes.
Change-Id: I5267e0bc68857fdc8a4b3384a2a1b0d37693ee6e
This commit is contained in:
Nick Kralevich 2017-02-14 09:49:30 -08:00
parent 0370905502
commit 125f1c0f22
1 changed files with 1 additions and 0 deletions

View File

@ -45,6 +45,7 @@ int faccessat(int dirfd, const char* pathname, int mode, int flags) {
if (flags != 0) { if (flags != 0) {
// We deliberately don't support AT_SYMLINK_NOFOLLOW, a glibc // We deliberately don't support AT_SYMLINK_NOFOLLOW, a glibc
// only feature which is error prone and dangerous. // only feature which is error prone and dangerous.
// More details at http://permalink.gmane.org/gmane.linux.lib.musl.general/6952
// //
// AT_EACCESS isn't supported either. Android doesn't have setuid // AT_EACCESS isn't supported either. Android doesn't have setuid
// programs, and never runs code with euid!=uid. It could be // programs, and never runs code with euid!=uid. It could be