[libcxx-commits] [PATCH] D92110: [SystemZ][ZOS] Provide PATH_MAX macro for libcxx
Louis Dionne via Phabricator via libcxx-commits
libcxx-commits at lists.llvm.org
Fri Dec 4 13:03:17 PST 2020
ldionne requested changes to this revision.
ldionne added inline comments.
This revision now requires changes to proceed.
Comment at: libcxx/src/filesystem/operations.cpp:545
+ #if defined(__MVS__)
+ char buff[1024 +1];
> Minor nit: style.
Hardcoding buffer sizes like that is a great way to trigger a buffer overflow when assumptions are not respected. I would much rather we don't introduce this sort of code in libc++, to be honest. Is there a reason why zOS can't just provide `PATH_MAX`?
Or, even much better, why doesn't zOS satisfy `defined(_POSIX_VERSION) && _POSIX_VERSION >= 200112`? Then, we could use the safe and non-buggy version of `realpath`. The buffer-taking version is documented in various places, including `realpath`'s manpage itself, as being buggy.
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
More information about the libcxx-commits