Neither EINVAL nor ENAMETOOLONG were bolded in the ERRORS section.
Signed-off-by: William Woodruff <william@tuffbizz.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
For the code that does this, see fs/dcache.c, search for
"prepend_unreachable".
Test case to demonstrate:
$ cat getcwd.c
int main(void) {
unshare(CLONE_NEWUSER | CLONE_NEWNS);
chdir("/usr");
chroot("bin");
printf("current directory: \"%s\"\n", get_current_dir_name());
char *real = realpath(".", NULL);
printf("realpath of .: \"%s\"\n", real ? real : "{none}");
real = realpath("../home/jann/.ssh", NULL);
printf("realpath of path: \"%s\"\n", real ? real : "{none}");
return 0;
}
$ cat getcwd_test.c
int main(void) {
unshare(CLONE_NEWUSER | CLONE_NEWNS);
chdir("/usr");
chroot("bin");
printf("current directory: \"%s\"\n", get_current_dir_name());
return 0;
}
$ gcc -o getcwd_test getcwd_test.c -Wall
$ ./getcwd_test
current directory: "(unreachable)/usr"
realpath.3 doesn't currently seem to handle this
case in a sane way, so I'm not going to document
its behavior yet. I'll report that as a bug instead.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The check for the slash at the start of a pathname is done in glibc
Reported-by: Fabien Pichot <fpichot@bouledef.eu>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The glibc pthread_sigqueue() function gives an error on attempts
to send either of the real-time signals used by NPTL.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The glibc pthread_kill() function gives an error on attempts
to send either of the real-time signals used by NPTL.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The glibc implementation silently ignores attempts to block the two
real-time signals used by NPTL.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Per IEEE-754 rounding rules.
The round(3) page describes the behavior of rint and nearbyint
in the halfway cases by saying:
These functions round x to the nearest integer, but round
halfway cases away from zero [...], instead of to the
nearest even integer like rint(3)
Signed-off-by: Matt Turner <mattst88@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Reported by Alexander Holler <holler@ahsoftware.de>
Signed-off-by: Stéphane Aulery <saulery@free.fr>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The current text says that unloading depends on whether
the reference count falls to zero *and no other libraries
are using symbols in this library*. That latter text has
been there since man-pages-1.29, but it seems rather dubious.
How could the implementation know whether other libraries
are still using symbols in this library? Furthermore, no
other implementation's man page mentions this point.
Seems best to drop this point.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This behavior is implementation-defined by POSIX. If the name
doesn't start with a '/', glibc returns EINVAL without attempting
the syscall.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions catanh(), catanhf() and catanhl() in glibc are thread safe.
It's markings match glibc markings.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions catan(), catanf() and catanl() are thread safe.
Their markings match glibc markings.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions' markings match glibc markings.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions canonicalize_file_name() in glibc is thread safe.
It's marking matches glibc marking.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Change the thread safety information to be the same as glibc.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
After researching and talking, we think inet_network() and
inet_ntoa() should be marked with locale.
After changing, the markings match glbc markings.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
After researching and talking, we think toupper() and tolower()
should not be marked with locale.
After changing, the markings match glbc markings.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions tgamma(), tgammaf() and tgammal() in glibc are thread safe.
It's markings match glibc markings.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The function fclose() is thread safe.
It's marking matches glibc marking.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions cpow(), cpowf() and cpowl() in glibc are thread safe.
It's markings match glibc markings.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions cosh(), coshf() and coshl() in glibc are thread safe.
It's markings match glibc markings.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The function closedir() in glibc is thread safe.
It's marking matches glibc marking.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions clog10(), clog10f() and clog10l() in glibc are thread safe.
It's markings match glibc markings.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The function cfree() in glibc is thread safe.
It's marking matches glibc marking.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions casinh(), casinhf() and casinhl() in glibc are thread safe.
It's markings match glibc markings.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions cacosh(), cacoshf() and cacoshl() in glibc are thread safe.
It's markings match glibc markings.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The function btowc() in glibc is thread safe.
It's marking matches glibc marking.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As this is man page for Linux, we don't need thread safety information
for bsd
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
According to the change of source code, ctermid's level has been
changed from MT-Unsafe to MT-Safe. After modifying, the marking
matches the glibc marking.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Zeng Linggang