On 02/24/2017 03:58 AM, Michael Kerrisk (man-pages) wrote: > So, what do other implementations do? Every other implementation that > I looked at, does return the lstat() information for the dangling > symlink. I looked at Solaris, OpenBSD, FreeBSD, and musl. All of this > strongly suggests that glibc got it wrong. Michael, Just because everyone else does it doesn't mean it's right, but it does argue strongly for a portability case or just cargo-culting from Solaris. However, what use case does that have? Why would you want the results of the lstat() if you specified !FTW_PHYS? It seems to me that the lstat() is a waste of resources if the caller is not interested in the results. I think the bug is in the POSIX spec and they should have said that the results of the stat buffer are undefined. This should go to the Austin Group for clarification. DJ, Could you please ask the Austin Group[1] to clarify what is the result of the stat buffer for dangling symlinks? Please post the bug once filed so the rest of us can comment and provide our own guidance. -- Cheers, Carlos. [1] http://austingroupbugs.net/main_page.php -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
