2007-04-29 14:05:22 +00:00
|
|
|
/*
|
|
|
|
* $FreeBSD$
|
|
|
|
*/
|
2006-03-13 00:53:21 +00:00
|
|
|
|
|
|
|
FBSD_1.0 {
|
|
|
|
__xuname;
|
|
|
|
pthread_atfork;
|
|
|
|
pthread_attr_destroy;
|
|
|
|
pthread_attr_getdetachstate;
|
|
|
|
pthread_attr_getguardsize;
|
|
|
|
pthread_attr_getinheritsched;
|
|
|
|
pthread_attr_getschedparam;
|
|
|
|
pthread_attr_getschedpolicy;
|
|
|
|
pthread_attr_getscope;
|
|
|
|
pthread_attr_getstackaddr;
|
|
|
|
pthread_attr_getstacksize;
|
|
|
|
pthread_attr_init;
|
|
|
|
pthread_attr_setdetachstate;
|
|
|
|
pthread_attr_setguardsize;
|
|
|
|
pthread_attr_setinheritsched;
|
|
|
|
pthread_attr_setschedparam;
|
|
|
|
pthread_attr_setschedpolicy;
|
|
|
|
pthread_attr_setscope;
|
|
|
|
pthread_attr_setstackaddr;
|
|
|
|
pthread_attr_setstacksize;
|
|
|
|
pthread_cancel;
|
|
|
|
pthread_cleanup_pop;
|
|
|
|
pthread_cleanup_push;
|
|
|
|
pthread_cond_broadcast;
|
|
|
|
pthread_cond_destroy;
|
|
|
|
pthread_cond_init;
|
|
|
|
pthread_cond_signal;
|
|
|
|
pthread_cond_timedwait;
|
|
|
|
pthread_cond_wait;
|
|
|
|
pthread_detach;
|
|
|
|
pthread_equal;
|
|
|
|
pthread_exit;
|
|
|
|
pthread_getspecific;
|
|
|
|
pthread_join;
|
|
|
|
pthread_key_create;
|
|
|
|
pthread_key_delete;
|
|
|
|
pthread_kill;
|
|
|
|
pthread_main_np;
|
|
|
|
pthread_mutex_destroy;
|
|
|
|
pthread_mutex_init;
|
|
|
|
pthread_mutex_lock;
|
|
|
|
pthread_mutex_trylock;
|
|
|
|
pthread_mutex_unlock;
|
|
|
|
pthread_mutexattr_destroy;
|
|
|
|
pthread_mutexattr_init;
|
|
|
|
pthread_mutexattr_settype;
|
|
|
|
pthread_once;
|
|
|
|
pthread_rwlock_destroy;
|
|
|
|
pthread_rwlock_init;
|
|
|
|
pthread_rwlock_rdlock;
|
|
|
|
pthread_rwlock_tryrdlock;
|
|
|
|
pthread_rwlock_trywrlock;
|
|
|
|
pthread_rwlock_unlock;
|
|
|
|
pthread_rwlock_wrlock;
|
|
|
|
pthread_self;
|
|
|
|
pthread_setcancelstate;
|
|
|
|
pthread_setcanceltype;
|
|
|
|
pthread_setspecific;
|
|
|
|
pthread_sigmask;
|
|
|
|
pthread_testcancel;
|
|
|
|
alarm;
|
|
|
|
arc4random;
|
|
|
|
__assert;
|
|
|
|
check_utility_compat;
|
|
|
|
clock;
|
|
|
|
closedir;
|
|
|
|
confstr;
|
|
|
|
ctermid;
|
|
|
|
ctermid_r;
|
|
|
|
daemon;
|
|
|
|
getdiskbyname;
|
|
|
|
dladdr;
|
|
|
|
dlclose;
|
|
|
|
dlerror;
|
|
|
|
dlfunc;
|
|
|
|
dllockinit;
|
|
|
|
dlopen;
|
|
|
|
dlsym;
|
|
|
|
dlvsym;
|
|
|
|
dlinfo;
|
2007-04-03 18:38:01 +00:00
|
|
|
dl_iterate_phdr;
|
2006-03-13 00:53:21 +00:00
|
|
|
drand48;
|
|
|
|
erand48;
|
|
|
|
err_set_file;
|
|
|
|
err_set_exit;
|
|
|
|
err;
|
|
|
|
verr;
|
|
|
|
errc;
|
|
|
|
verrc;
|
|
|
|
errx;
|
|
|
|
verrx;
|
|
|
|
warn;
|
|
|
|
vwarn;
|
|
|
|
warnc;
|
|
|
|
vwarnc;
|
|
|
|
warnx;
|
|
|
|
vwarnx;
|
|
|
|
sys_errlist;
|
|
|
|
sys_nerr;
|
|
|
|
errno;
|
2018-04-12 18:23:14 +00:00
|
|
|
exect;
|
2006-03-13 00:53:21 +00:00
|
|
|
execl;
|
|
|
|
execle;
|
|
|
|
execlp;
|
|
|
|
execv;
|
|
|
|
execvp;
|
|
|
|
execvP;
|
|
|
|
fmtcheck;
|
|
|
|
fmtmsg;
|
|
|
|
fnmatch;
|
|
|
|
__fpclassifyf;
|
|
|
|
__fpclassifyd;
|
|
|
|
__fpclassifyl;
|
|
|
|
frexp;
|
|
|
|
setfstab;
|
|
|
|
getfstab;
|
|
|
|
getfsent;
|
|
|
|
getfsspec;
|
|
|
|
getfsfile;
|
|
|
|
setfsent;
|
|
|
|
endfsent;
|
|
|
|
ftok;
|
|
|
|
getbootfile;
|
|
|
|
getbsize;
|
|
|
|
cgetset;
|
|
|
|
cgetcap;
|
|
|
|
cgetent;
|
|
|
|
cgetmatch;
|
|
|
|
cgetfirst;
|
|
|
|
cgetclose;
|
|
|
|
cgetnext;
|
|
|
|
cgetstr;
|
|
|
|
cgetustr;
|
|
|
|
cgetnum;
|
|
|
|
getcwd;
|
|
|
|
getdomainname;
|
|
|
|
setgrent;
|
|
|
|
setgroupent;
|
|
|
|
endgrent;
|
|
|
|
getgrent_r;
|
|
|
|
getgrnam_r;
|
|
|
|
getgrgid_r;
|
|
|
|
getgrnam;
|
|
|
|
getgrgid;
|
|
|
|
getgrent;
|
2007-04-29 14:05:22 +00:00
|
|
|
/*
|
|
|
|
* Why are __gr_parse_entry() and __gr_match_entry() not static in
|
|
|
|
* gen/getgrent.c?
|
|
|
|
*/
|
2006-03-13 00:53:21 +00:00
|
|
|
getgrouplist;
|
|
|
|
gethostname;
|
|
|
|
getloadavg;
|
|
|
|
getlogin;
|
|
|
|
getlogin_r;
|
|
|
|
setnetgrent;
|
|
|
|
getnetgrent;
|
|
|
|
endnetgrent;
|
|
|
|
innetgr;
|
|
|
|
getosreldate;
|
|
|
|
getpagesize;
|
|
|
|
getpeereid;
|
|
|
|
_getprogname;
|
|
|
|
getprogname;
|
|
|
|
setpwent;
|
|
|
|
setpassent;
|
|
|
|
endpwent;
|
|
|
|
getpwent_r;
|
|
|
|
getpwnam_r;
|
|
|
|
getpwuid_r;
|
|
|
|
getpwnam;
|
|
|
|
getpwuid;
|
|
|
|
getpwent;
|
|
|
|
getttynam;
|
|
|
|
getttyent;
|
|
|
|
setttyent;
|
|
|
|
endttyent;
|
|
|
|
isdialuptty;
|
|
|
|
isnettty;
|
|
|
|
getusershell;
|
|
|
|
endusershell;
|
|
|
|
setusershell;
|
|
|
|
getvfsbyname;
|
|
|
|
__isnan;
|
|
|
|
isnan;
|
|
|
|
__isnanf;
|
|
|
|
isnanf;
|
|
|
|
__isinf;
|
|
|
|
isinf;
|
|
|
|
__isinff;
|
|
|
|
__isinfl;
|
|
|
|
isatty;
|
|
|
|
initgroups;
|
|
|
|
jrand48;
|
|
|
|
lcong48;
|
|
|
|
ldexp;
|
|
|
|
lockf;
|
|
|
|
lrand48;
|
2011-10-21 06:40:36 +00:00
|
|
|
modf;
|
2006-03-13 00:53:21 +00:00
|
|
|
mrand48;
|
|
|
|
nice;
|
|
|
|
nlist;
|
|
|
|
nrand48;
|
|
|
|
opendir;
|
|
|
|
pause;
|
|
|
|
posix_madvise;
|
|
|
|
popen;
|
|
|
|
pclose;
|
|
|
|
psignal;
|
|
|
|
raise;
|
|
|
|
readpassphrase;
|
|
|
|
getpass;
|
|
|
|
rewinddir;
|
|
|
|
seed48;
|
|
|
|
seekdir;
|
|
|
|
user_from_uid;
|
|
|
|
group_from_gid;
|
|
|
|
setdomainname;
|
|
|
|
sethostname;
|
|
|
|
longjmperror;
|
|
|
|
getmode;
|
|
|
|
setmode;
|
|
|
|
setproctitle;
|
|
|
|
setprogname;
|
|
|
|
siginterrupt;
|
|
|
|
sys_signame;
|
|
|
|
sys_siglist;
|
|
|
|
sys_nsig;
|
|
|
|
signal;
|
|
|
|
sigaddset;
|
|
|
|
sigdelset;
|
|
|
|
sigemptyset;
|
|
|
|
sigfillset;
|
|
|
|
sigismember;
|
|
|
|
sleep;
|
|
|
|
srand48;
|
|
|
|
fstatvfs;
|
|
|
|
statvfs;
|
|
|
|
sl_init;
|
|
|
|
sl_add;
|
|
|
|
sl_free;
|
|
|
|
sl_find;
|
|
|
|
fflagstostr;
|
|
|
|
strtofflags;
|
|
|
|
sysconf;
|
|
|
|
sysctl;
|
|
|
|
sysctlbyname;
|
|
|
|
sysctlnametomib;
|
|
|
|
syslog;
|
|
|
|
vsyslog;
|
|
|
|
openlog;
|
|
|
|
closelog;
|
|
|
|
setlogmask;
|
|
|
|
ttyname_r;
|
|
|
|
ttyname;
|
|
|
|
timezone;
|
|
|
|
times;
|
|
|
|
time;
|
|
|
|
telldir;
|
|
|
|
tcgetattr;
|
|
|
|
tcsetattr;
|
|
|
|
tcsetpgrp;
|
|
|
|
tcgetpgrp;
|
|
|
|
cfgetospeed;
|
|
|
|
cfgetispeed;
|
|
|
|
cfsetospeed;
|
|
|
|
cfsetispeed;
|
|
|
|
cfsetspeed;
|
|
|
|
cfmakeraw;
|
|
|
|
tcsendbreak;
|
|
|
|
_init_tls;
|
2007-04-29 14:05:22 +00:00
|
|
|
__tls_get_addr;
|
2006-03-13 00:53:21 +00:00
|
|
|
tcdrain;
|
|
|
|
tcflush;
|
|
|
|
tcflow;
|
|
|
|
ualarm;
|
|
|
|
ulimit;
|
2010-01-19 23:07:12 +00:00
|
|
|
uname;
|
2013-01-11 15:50:01 +00:00
|
|
|
strunvis;
|
|
|
|
strunvisx;
|
2006-03-13 00:53:21 +00:00
|
|
|
usleep;
|
|
|
|
utime;
|
|
|
|
valloc;
|
|
|
|
vis;
|
|
|
|
strvis;
|
|
|
|
strvisx;
|
|
|
|
wait;
|
|
|
|
wait3;
|
|
|
|
waitpid;
|
|
|
|
wordexp;
|
|
|
|
wordfree;
|
|
|
|
};
|
|
|
|
|
Our fts(3) API, as inherited from 4.4BSD, suffers from integer
fields in FTS and FTSENT structs being too narrow. In addition,
the narrow types creep from there into fts.c. As a result, fts(3)
consumers, e.g., find(1) or rm(1), can't handle file trees an ordinary
user can create, which can have security implications.
To fix the historic implementation of fts(3), OpenBSD and NetBSD
have already changed <fts.h> in somewhat incompatible ways, so we
are free to do so, too. This change is a superset of changes from
the other BSDs with a few more improvements. It doesn't touch
fts(3) functionality; it just extends integer types used by it to
match modern reality and the C standard.
Here are its points:
o For C object sizes, use size_t unless it's 100% certain that
the object will be really small. (Note that fts(3) can construct
pathnames _much_ longer than PATH_MAX for its consumers.)
o Avoid the short types because on modern platforms using them
results in larger and slower code. Change shorts to ints as
follows:
- For variables than count simple, limited things like states,
use plain vanilla `int' as it's the type of choice in C.
- For a limited number of bit flags use `unsigned' because signed
bit-wise operations are implementation-defined, i.e., unportable,
in C.
o For things that should be at least 64 bits wide, use long long
and not int64_t, as the latter is an optional type. See
FTSENT.fts_number aka FTS.fts_bignum. Extending fts_number `to
satisfy future needs' is pointless because there is fts_pointer,
which can be used to link to arbitrary data from an FTSENT.
However, there already are fts(3) consumers that require fts_number,
or fts_bignum, have at least 64 bits in it, so we must allow for them.
o For the tree depth, use `long'. This is a trade-off between making
this field too wide and allowing for 64-bit inode numbers and/or
chain-mounted filesystems. On the one hand, `long' is almost
enough for 32-bit filesystems on a 32-bit platform (our ino_t is
uint32_t now). On the other hand, platforms with a 64-bit (or
wider) `long' will be ready for 64-bit inode numbers, as well as
for several 32-bit filesystems mounted one under another. Note
that fts_level has to be signed because -1 is a magic value for it,
FTS_ROOTPARENTLEVEL.
o For the `nlinks' local var in fts_build(), use `long'. The logic
in fts_build() requires that `nlinks' be signed, but our nlink_t
currently is uint16_t. Therefore let's make the signed var wide
enough to be able to represent 2^16-1 in pure C99, and even 2^32-1
on a 64-bit platform. Perhaps the logic should be changed just
to use nlink_t, but it can be done later w/o breaking fts(3) ABI
any more because `nlinks' is just a local var.
This commit also inludes supporting stuff for the fts change:
o Preserve the old versions of fts(3) functions through libc symbol
versioning because the old versions appeared in all our former releases.
o Bump __FreeBSD_version just in case. There is a small chance that
some ill-written 3-rd party apps may fail to build or work correctly
if compiled after this change.
o Update the fts(3) manpage accordingly. In particular, remove
references to fts_bignum, which was a FreeBSD-specific hack to work
around the too narrow types of FTSENT members. Now fts_number is
at least 64 bits wide (long long) and fts_bignum is an undocumented
alias for fts_number kept around for compatibility reasons. According
to Google Code Search, the only big consumers of fts_bignum are in
our own source tree, so they can be fixed easily to use fts_number.
o Mention the change in src/UPDATING.
PR: bin/104458
Approved by: re (quite a while ago)
Discussed with: deischen (the symbol versioning part)
Reviewed by: -arch (mostly silence); das (generally OK, but we didn't
agree on some types used; assuming that no objections on
-arch let me to stick to my opinion)
2008-01-26 17:09:40 +00:00
|
|
|
FBSD_1.1 {
|
2008-07-21 18:03:31 +00:00
|
|
|
arc4random_buf;
|
2008-07-22 11:33:49 +00:00
|
|
|
arc4random_uniform;
|
2009-02-11 20:24:59 +00:00
|
|
|
fdevname;
|
|
|
|
fdevname_r;
|
2008-04-16 18:59:36 +00:00
|
|
|
fdopendir;
|
2008-07-21 22:07:59 +00:00
|
|
|
feature_present;
|
2009-05-04 08:06:52 +00:00
|
|
|
posix_spawn;
|
|
|
|
posix_spawn_file_actions_addclose;
|
|
|
|
posix_spawn_file_actions_adddup2;
|
|
|
|
posix_spawn_file_actions_addopen;
|
|
|
|
posix_spawn_file_actions_destroy;
|
|
|
|
posix_spawn_file_actions_init;
|
|
|
|
posix_spawnattr_destroy;
|
|
|
|
posix_spawnattr_getflags;
|
|
|
|
posix_spawnattr_getpgroup;
|
|
|
|
posix_spawnattr_getschedparam;
|
|
|
|
posix_spawnattr_getschedpolicy;
|
|
|
|
posix_spawnattr_getsigdefault;
|
|
|
|
posix_spawnattr_getsigmask;
|
|
|
|
posix_spawnattr_init;
|
|
|
|
posix_spawnattr_setflags;
|
|
|
|
posix_spawnattr_setpgroup;
|
|
|
|
posix_spawnattr_setschedparam;
|
|
|
|
posix_spawnattr_setschedpolicy;
|
|
|
|
posix_spawnattr_setsigdefault;
|
|
|
|
posix_spawnattr_setsigmask;
|
|
|
|
posix_spawnp;
|
2009-06-24 21:10:52 +00:00
|
|
|
semctl;
|
2008-04-15 08:33:32 +00:00
|
|
|
tcgetsid;
|
2009-05-07 13:49:48 +00:00
|
|
|
tcsetsid;
|
Use umtx to implement process sharable semaphore, to make this work,
now type sema_t is a structure which can be put in a shared memory area,
and multiple processes can operate it concurrently.
User can either use mmap(MAP_SHARED) + sem_init(pshared=1) or use sem_open()
to initialize a shared semaphore.
Named semaphore uses file system and is located in /tmp directory, and its
file name is prefixed with 'SEMD', so now it is chroot or jail friendly.
In simplist cases, both for named and un-named semaphore, userland code
does not have to enter kernel to reduce/increase semaphore's count.
The semaphore is designed to be crash-safe, it means even if an application
is crashed in the middle of operating semaphore, the semaphore state is
still safely recovered by later use, there is no waiter counter maintained
by userland code.
The main semaphore code is in libc and libthr only has some necessary stubs,
this makes it possible that a non-threaded application can use semaphore
without linking to thread library.
Old semaphore implementation is kept libc to maintain binary compatibility.
The kernel ksem API is no longer used in the new implemenation.
Discussed on: threads@
2010-01-05 02:37:59 +00:00
|
|
|
__pthread_cleanup_pop_imp;
|
|
|
|
__pthread_cleanup_push_imp;
|
Our fts(3) API, as inherited from 4.4BSD, suffers from integer
fields in FTS and FTSENT structs being too narrow. In addition,
the narrow types creep from there into fts.c. As a result, fts(3)
consumers, e.g., find(1) or rm(1), can't handle file trees an ordinary
user can create, which can have security implications.
To fix the historic implementation of fts(3), OpenBSD and NetBSD
have already changed <fts.h> in somewhat incompatible ways, so we
are free to do so, too. This change is a superset of changes from
the other BSDs with a few more improvements. It doesn't touch
fts(3) functionality; it just extends integer types used by it to
match modern reality and the C standard.
Here are its points:
o For C object sizes, use size_t unless it's 100% certain that
the object will be really small. (Note that fts(3) can construct
pathnames _much_ longer than PATH_MAX for its consumers.)
o Avoid the short types because on modern platforms using them
results in larger and slower code. Change shorts to ints as
follows:
- For variables than count simple, limited things like states,
use plain vanilla `int' as it's the type of choice in C.
- For a limited number of bit flags use `unsigned' because signed
bit-wise operations are implementation-defined, i.e., unportable,
in C.
o For things that should be at least 64 bits wide, use long long
and not int64_t, as the latter is an optional type. See
FTSENT.fts_number aka FTS.fts_bignum. Extending fts_number `to
satisfy future needs' is pointless because there is fts_pointer,
which can be used to link to arbitrary data from an FTSENT.
However, there already are fts(3) consumers that require fts_number,
or fts_bignum, have at least 64 bits in it, so we must allow for them.
o For the tree depth, use `long'. This is a trade-off between making
this field too wide and allowing for 64-bit inode numbers and/or
chain-mounted filesystems. On the one hand, `long' is almost
enough for 32-bit filesystems on a 32-bit platform (our ino_t is
uint32_t now). On the other hand, platforms with a 64-bit (or
wider) `long' will be ready for 64-bit inode numbers, as well as
for several 32-bit filesystems mounted one under another. Note
that fts_level has to be signed because -1 is a magic value for it,
FTS_ROOTPARENTLEVEL.
o For the `nlinks' local var in fts_build(), use `long'. The logic
in fts_build() requires that `nlinks' be signed, but our nlink_t
currently is uint16_t. Therefore let's make the signed var wide
enough to be able to represent 2^16-1 in pure C99, and even 2^32-1
on a 64-bit platform. Perhaps the logic should be changed just
to use nlink_t, but it can be done later w/o breaking fts(3) ABI
any more because `nlinks' is just a local var.
This commit also inludes supporting stuff for the fts change:
o Preserve the old versions of fts(3) functions through libc symbol
versioning because the old versions appeared in all our former releases.
o Bump __FreeBSD_version just in case. There is a small chance that
some ill-written 3-rd party apps may fail to build or work correctly
if compiled after this change.
o Update the fts(3) manpage accordingly. In particular, remove
references to fts_bignum, which was a FreeBSD-specific hack to work
around the too narrow types of FTSENT members. Now fts_number is
at least 64 bits wide (long long) and fts_bignum is an undocumented
alias for fts_number kept around for compatibility reasons. According
to Google Code Search, the only big consumers of fts_bignum are in
our own source tree, so they can be fixed easily to use fts_number.
o Mention the change in src/UPDATING.
PR: bin/104458
Approved by: re (quite a while ago)
Discussed with: deischen (the symbol versioning part)
Reviewed by: -arch (mostly silence); das (generally OK, but we didn't
agree on some types used; assuming that no objections on
-arch let me to stick to my opinion)
2008-01-26 17:09:40 +00:00
|
|
|
};
|
|
|
|
|
2009-09-19 18:01:32 +00:00
|
|
|
FBSD_1.2 {
|
2010-11-02 17:00:56 +00:00
|
|
|
cfmakesane;
|
2010-01-13 17:29:55 +00:00
|
|
|
endutxent;
|
2009-09-19 18:01:32 +00:00
|
|
|
getpagesizes;
|
2010-01-13 17:29:55 +00:00
|
|
|
getutxent;
|
|
|
|
getutxid;
|
|
|
|
getutxline;
|
|
|
|
getutxuser;
|
|
|
|
pututxline;
|
Use umtx to implement process sharable semaphore, to make this work,
now type sema_t is a structure which can be put in a shared memory area,
and multiple processes can operate it concurrently.
User can either use mmap(MAP_SHARED) + sem_init(pshared=1) or use sem_open()
to initialize a shared semaphore.
Named semaphore uses file system and is located in /tmp directory, and its
file name is prefixed with 'SEMD', so now it is chroot or jail friendly.
In simplist cases, both for named and un-named semaphore, userland code
does not have to enter kernel to reduce/increase semaphore's count.
The semaphore is designed to be crash-safe, it means even if an application
is crashed in the middle of operating semaphore, the semaphore state is
still safely recovered by later use, there is no waiter counter maintained
by userland code.
The main semaphore code is in libc and libthr only has some necessary stubs,
this makes it possible that a non-threaded application can use semaphore
without linking to thread library.
Old semaphore implementation is kept libc to maintain binary compatibility.
The kernel ksem API is no longer used in the new implemenation.
Discussed on: threads@
2010-01-05 02:37:59 +00:00
|
|
|
sem_close;
|
|
|
|
sem_destroy;
|
|
|
|
sem_getvalue;
|
|
|
|
sem_init;
|
|
|
|
sem_open;
|
2010-01-13 17:29:55 +00:00
|
|
|
sem_post;
|
Use umtx to implement process sharable semaphore, to make this work,
now type sema_t is a structure which can be put in a shared memory area,
and multiple processes can operate it concurrently.
User can either use mmap(MAP_SHARED) + sem_init(pshared=1) or use sem_open()
to initialize a shared semaphore.
Named semaphore uses file system and is located in /tmp directory, and its
file name is prefixed with 'SEMD', so now it is chroot or jail friendly.
In simplist cases, both for named and un-named semaphore, userland code
does not have to enter kernel to reduce/increase semaphore's count.
The semaphore is designed to be crash-safe, it means even if an application
is crashed in the middle of operating semaphore, the semaphore state is
still safely recovered by later use, there is no waiter counter maintained
by userland code.
The main semaphore code is in libc and libthr only has some necessary stubs,
this makes it possible that a non-threaded application can use semaphore
without linking to thread library.
Old semaphore implementation is kept libc to maintain binary compatibility.
The kernel ksem API is no longer used in the new implemenation.
Discussed on: threads@
2010-01-05 02:37:59 +00:00
|
|
|
sem_timedwait;
|
|
|
|
sem_trywait;
|
|
|
|
sem_unlink;
|
2010-01-13 17:29:55 +00:00
|
|
|
sem_wait;
|
|
|
|
setutxdb;
|
|
|
|
setutxent;
|
2009-09-19 18:01:32 +00:00
|
|
|
};
|
|
|
|
|
2011-12-23 15:00:37 +00:00
|
|
|
FBSD_1.3 {
|
2012-08-17 02:26:31 +00:00
|
|
|
clock_getcpuclockid;
|
2012-05-19 12:44:27 +00:00
|
|
|
dirfd;
|
2013-08-16 13:10:30 +00:00
|
|
|
dup3;
|
2013-08-18 20:11:34 +00:00
|
|
|
fdclosedir;
|
2013-08-18 20:06:35 +00:00
|
|
|
fdlopen;
|
2011-12-23 15:00:37 +00:00
|
|
|
__FreeBSD_libc_enter_restricted_mode;
|
2012-01-21 18:00:28 +00:00
|
|
|
getcontextx;
|
2012-10-19 12:44:22 +00:00
|
|
|
gid_from_group;
|
2012-12-18 16:37:24 +00:00
|
|
|
nvis;
|
2012-10-19 12:44:22 +00:00
|
|
|
pwcache_userdb;
|
|
|
|
pwcache_groupdb;
|
2012-12-18 16:37:24 +00:00
|
|
|
snvis;
|
2013-03-14 23:51:47 +00:00
|
|
|
strenvisx;
|
2012-12-18 16:37:24 +00:00
|
|
|
strnunvis;
|
|
|
|
strnunvisx;
|
|
|
|
strnvis;
|
|
|
|
strnvisx;
|
2013-03-14 23:51:47 +00:00
|
|
|
strsenvisx;
|
2012-12-18 16:37:24 +00:00
|
|
|
strsnvis;
|
|
|
|
strsnvisx;
|
|
|
|
strsvis;
|
|
|
|
strsvisx;
|
|
|
|
svis;
|
2012-10-19 12:44:22 +00:00
|
|
|
uid_from_user;
|
2012-12-18 16:37:24 +00:00
|
|
|
unvis;
|
2012-11-13 12:55:52 +00:00
|
|
|
waitid;
|
2011-12-23 15:00:37 +00:00
|
|
|
};
|
|
|
|
|
2014-04-03 08:16:45 +00:00
|
|
|
FBSD_1.4 {
|
2016-06-09 01:28:44 +00:00
|
|
|
getnetgrent_r;
|
Add implementation of robust mutexes, hopefully close enough to the
intention of the POSIX IEEE Std 1003.1TM-2008/Cor 1-2013.
A robust mutex is guaranteed to be cleared by the system upon either
thread or process owner termination while the mutex is held. The next
mutex locker is then notified about inconsistent mutex state and can
execute (or abandon) corrective actions.
The patch mostly consists of small changes here and there, adding
neccessary checks for the inconsistent and abandoned conditions into
existing paths. Additionally, the thread exit handler was extended to
iterate over the userspace-maintained list of owned robust mutexes,
unlocking and marking as terminated each of them.
The list of owned robust mutexes cannot be maintained atomically
synchronous with the mutex lock state (it is possible in kernel, but
is too expensive). Instead, for the duration of lock or unlock
operation, the current mutex is remembered in a special slot that is
also checked by the kernel at thread termination.
Kernel must be aware about the per-thread location of the heads of
robust mutex lists and the current active mutex slot. When a thread
touches a robust mutex for the first time, a new umtx op syscall is
issued which informs about location of lists heads.
The umtx sleep queues for PP and PI mutexes are split between
non-robust and robust.
Somewhat unrelated changes in the patch:
1. Style.
2. The fix for proper tdfind() call use in umtxq_sleep_pi() for shared
pi mutexes.
3. Removal of the userspace struct pthread_mutex m_owner field.
4. The sysctl kern.ipc.umtx_vnode_persistent is added, which controls
the lifetime of the shared mutex associated with a vnode' page.
Reviewed by: jilles (previous version, supposedly the objection was fixed)
Discussed with: brooks, Martin Simmons <martin@lispworks.com> (some aspects)
Tested by: pho
Sponsored by: The FreeBSD Foundation
2016-05-17 09:56:22 +00:00
|
|
|
pthread_mutex_consistent;
|
|
|
|
pthread_mutexattr_getrobust;
|
|
|
|
pthread_mutexattr_setrobust;
|
2016-06-08 18:21:27 +00:00
|
|
|
stravis;
|
2014-04-03 08:16:45 +00:00
|
|
|
};
|
|
|
|
|
2016-08-12 07:03:58 +00:00
|
|
|
FBSD_1.5 {
|
Commit the 64-bit inode project.
Extend the ino_t, dev_t, nlink_t types to 64-bit ints. Modify
struct dirent layout to add d_off, increase the size of d_fileno
to 64-bits, increase the size of d_namlen to 16-bits, and change
the required alignment. Increase struct statfs f_mntfromname[] and
f_mntonname[] array length MNAMELEN to 1024.
ABI breakage is mitigated by providing compatibility using versioned
symbols, ingenious use of the existing padding in structures, and
by employing other tricks. Unfortunately, not everything can be
fixed, especially outside the base system. For instance, third-party
APIs which pass struct stat around are broken in backward and
forward incompatible ways.
Kinfo sysctl MIBs ABI is changed in backward-compatible way, but
there is no general mechanism to handle other sysctl MIBS which
return structures where the layout has changed. It was considered
that the breakage is either in the management interfaces, where we
usually allow ABI slip, or is not important.
Struct xvnode changed layout, no compat shims are provided.
For struct xtty, dev_t tty device member was reduced to uint32_t.
It was decided that keeping ABI compat in this case is more useful
than reporting 64-bit dev_t, for the sake of pstat.
Update note: strictly follow the instructions in UPDATING. Build
and install the new kernel with COMPAT_FREEBSD11 option enabled,
then reboot, and only then install new world.
Credits: The 64-bit inode project, also known as ino64, started life
many years ago as a project by Gleb Kurtsou (gleb). Kirk McKusick
(mckusick) then picked up and updated the patch, and acted as a
flag-waver. Feedback, suggestions, and discussions were carried
by Ed Maste (emaste), John Baldwin (jhb), Jilles Tjoelker (jilles),
and Rick Macklem (rmacklem). Kris Moore (kris) performed an initial
ports investigation followed by an exp-run by Antoine Brodin (antoine).
Essential and all-embracing testing was done by Peter Holm (pho).
The heavy lifting of coordinating all these efforts and bringing the
project to completion were done by Konstantin Belousov (kib).
Sponsored by: The FreeBSD Foundation (emaste, kib)
Differential revision: https://reviews.freebsd.org/D10439
2017-05-23 09:29:05 +00:00
|
|
|
alphasort;
|
2016-11-03 20:21:34 +00:00
|
|
|
basename;
|
2017-12-23 18:07:43 +00:00
|
|
|
daemonfd;
|
Commit the 64-bit inode project.
Extend the ino_t, dev_t, nlink_t types to 64-bit ints. Modify
struct dirent layout to add d_off, increase the size of d_fileno
to 64-bits, increase the size of d_namlen to 16-bits, and change
the required alignment. Increase struct statfs f_mntfromname[] and
f_mntonname[] array length MNAMELEN to 1024.
ABI breakage is mitigated by providing compatibility using versioned
symbols, ingenious use of the existing padding in structures, and
by employing other tricks. Unfortunately, not everything can be
fixed, especially outside the base system. For instance, third-party
APIs which pass struct stat around are broken in backward and
forward incompatible ways.
Kinfo sysctl MIBs ABI is changed in backward-compatible way, but
there is no general mechanism to handle other sysctl MIBS which
return structures where the layout has changed. It was considered
that the breakage is either in the management interfaces, where we
usually allow ABI slip, or is not important.
Struct xvnode changed layout, no compat shims are provided.
For struct xtty, dev_t tty device member was reduced to uint32_t.
It was decided that keeping ABI compat in this case is more useful
than reporting 64-bit dev_t, for the sake of pstat.
Update note: strictly follow the instructions in UPDATING. Build
and install the new kernel with COMPAT_FREEBSD11 option enabled,
then reboot, and only then install new world.
Credits: The 64-bit inode project, also known as ino64, started life
many years ago as a project by Gleb Kurtsou (gleb). Kirk McKusick
(mckusick) then picked up and updated the patch, and acted as a
flag-waver. Feedback, suggestions, and discussions were carried
by Ed Maste (emaste), John Baldwin (jhb), Jilles Tjoelker (jilles),
and Rick Macklem (rmacklem). Kris Moore (kris) performed an initial
ports investigation followed by an exp-run by Antoine Brodin (antoine).
Essential and all-embracing testing was done by Peter Holm (pho).
The heavy lifting of coordinating all these efforts and bringing the
project to completion were done by Konstantin Belousov (kib).
Sponsored by: The FreeBSD Foundation (emaste, kib)
Differential revision: https://reviews.freebsd.org/D10439
2017-05-23 09:29:05 +00:00
|
|
|
devname;
|
|
|
|
devname_r;
|
2016-08-12 07:03:58 +00:00
|
|
|
dirname;
|
2017-10-21 12:06:18 +00:00
|
|
|
elf_aux_info;
|
Commit the 64-bit inode project.
Extend the ino_t, dev_t, nlink_t types to 64-bit ints. Modify
struct dirent layout to add d_off, increase the size of d_fileno
to 64-bits, increase the size of d_namlen to 16-bits, and change
the required alignment. Increase struct statfs f_mntfromname[] and
f_mntonname[] array length MNAMELEN to 1024.
ABI breakage is mitigated by providing compatibility using versioned
symbols, ingenious use of the existing padding in structures, and
by employing other tricks. Unfortunately, not everything can be
fixed, especially outside the base system. For instance, third-party
APIs which pass struct stat around are broken in backward and
forward incompatible ways.
Kinfo sysctl MIBs ABI is changed in backward-compatible way, but
there is no general mechanism to handle other sysctl MIBS which
return structures where the layout has changed. It was considered
that the breakage is either in the management interfaces, where we
usually allow ABI slip, or is not important.
Struct xvnode changed layout, no compat shims are provided.
For struct xtty, dev_t tty device member was reduced to uint32_t.
It was decided that keeping ABI compat in this case is more useful
than reporting 64-bit dev_t, for the sake of pstat.
Update note: strictly follow the instructions in UPDATING. Build
and install the new kernel with COMPAT_FREEBSD11 option enabled,
then reboot, and only then install new world.
Credits: The 64-bit inode project, also known as ino64, started life
many years ago as a project by Gleb Kurtsou (gleb). Kirk McKusick
(mckusick) then picked up and updated the patch, and acted as a
flag-waver. Feedback, suggestions, and discussions were carried
by Ed Maste (emaste), John Baldwin (jhb), Jilles Tjoelker (jilles),
and Rick Macklem (rmacklem). Kris Moore (kris) performed an initial
ports investigation followed by an exp-run by Antoine Brodin (antoine).
Essential and all-embracing testing was done by Peter Holm (pho).
The heavy lifting of coordinating all these efforts and bringing the
project to completion were done by Konstantin Belousov (kib).
Sponsored by: The FreeBSD Foundation (emaste, kib)
Differential revision: https://reviews.freebsd.org/D10439
2017-05-23 09:29:05 +00:00
|
|
|
fts_children;
|
|
|
|
fts_close;
|
|
|
|
fts_get_clientptr;
|
|
|
|
fts_get_stream;
|
|
|
|
fts_open;
|
|
|
|
fts_read;
|
|
|
|
fts_set;
|
|
|
|
fts_set_clientptr;
|
|
|
|
ftw;
|
2018-03-21 01:15:45 +00:00
|
|
|
getentropy;
|
Commit the 64-bit inode project.
Extend the ino_t, dev_t, nlink_t types to 64-bit ints. Modify
struct dirent layout to add d_off, increase the size of d_fileno
to 64-bits, increase the size of d_namlen to 16-bits, and change
the required alignment. Increase struct statfs f_mntfromname[] and
f_mntonname[] array length MNAMELEN to 1024.
ABI breakage is mitigated by providing compatibility using versioned
symbols, ingenious use of the existing padding in structures, and
by employing other tricks. Unfortunately, not everything can be
fixed, especially outside the base system. For instance, third-party
APIs which pass struct stat around are broken in backward and
forward incompatible ways.
Kinfo sysctl MIBs ABI is changed in backward-compatible way, but
there is no general mechanism to handle other sysctl MIBS which
return structures where the layout has changed. It was considered
that the breakage is either in the management interfaces, where we
usually allow ABI slip, or is not important.
Struct xvnode changed layout, no compat shims are provided.
For struct xtty, dev_t tty device member was reduced to uint32_t.
It was decided that keeping ABI compat in this case is more useful
than reporting 64-bit dev_t, for the sake of pstat.
Update note: strictly follow the instructions in UPDATING. Build
and install the new kernel with COMPAT_FREEBSD11 option enabled,
then reboot, and only then install new world.
Credits: The 64-bit inode project, also known as ino64, started life
many years ago as a project by Gleb Kurtsou (gleb). Kirk McKusick
(mckusick) then picked up and updated the patch, and acted as a
flag-waver. Feedback, suggestions, and discussions were carried
by Ed Maste (emaste), John Baldwin (jhb), Jilles Tjoelker (jilles),
and Rick Macklem (rmacklem). Kris Moore (kris) performed an initial
ports investigation followed by an exp-run by Antoine Brodin (antoine).
Essential and all-embracing testing was done by Peter Holm (pho).
The heavy lifting of coordinating all these efforts and bringing the
project to completion were done by Konstantin Belousov (kib).
Sponsored by: The FreeBSD Foundation (emaste, kib)
Differential revision: https://reviews.freebsd.org/D10439
2017-05-23 09:29:05 +00:00
|
|
|
getmntinfo;
|
|
|
|
glob;
|
|
|
|
globfree;
|
|
|
|
nftw;
|
|
|
|
readdir;
|
|
|
|
readdir_r;
|
|
|
|
scandir;
|
|
|
|
scandir_b;
|
2017-02-23 19:36:38 +00:00
|
|
|
sem_clockwait_np;
|
2018-07-04 13:31:16 +00:00
|
|
|
setproctitle_fast;
|
2018-08-10 15:16:30 +00:00
|
|
|
timespec_get;
|
2016-08-12 07:03:58 +00:00
|
|
|
};
|
|
|
|
|
2007-04-29 14:05:22 +00:00
|
|
|
FBSDprivate_1.0 {
|
|
|
|
/* needed by thread libraries */
|
2006-03-13 00:53:21 +00:00
|
|
|
__thr_jtable;
|
|
|
|
|
|
|
|
_pthread_atfork;
|
|
|
|
_pthread_attr_destroy;
|
|
|
|
_pthread_attr_getdetachstate;
|
|
|
|
_pthread_attr_getguardsize;
|
|
|
|
_pthread_attr_getinheritsched;
|
|
|
|
_pthread_attr_getschedparam;
|
|
|
|
_pthread_attr_getschedpolicy;
|
|
|
|
_pthread_attr_getscope;
|
|
|
|
_pthread_attr_getstackaddr;
|
|
|
|
_pthread_attr_getstacksize;
|
|
|
|
_pthread_attr_init;
|
|
|
|
_pthread_attr_setdetachstate;
|
|
|
|
_pthread_attr_setguardsize;
|
|
|
|
_pthread_attr_setinheritsched;
|
|
|
|
_pthread_attr_setschedparam;
|
|
|
|
_pthread_attr_setschedpolicy;
|
|
|
|
_pthread_attr_setscope;
|
|
|
|
_pthread_attr_setstackaddr;
|
|
|
|
_pthread_attr_setstacksize;
|
|
|
|
_pthread_cancel;
|
2010-09-25 01:57:47 +00:00
|
|
|
_pthread_cancel_enter;
|
|
|
|
_pthread_cancel_leave;
|
2006-03-13 00:53:21 +00:00
|
|
|
_pthread_cleanup_pop;
|
|
|
|
_pthread_cleanup_push;
|
|
|
|
_pthread_cond_broadcast;
|
|
|
|
_pthread_cond_destroy;
|
|
|
|
_pthread_cond_init;
|
|
|
|
_pthread_cond_signal;
|
|
|
|
_pthread_cond_timedwait;
|
|
|
|
_pthread_cond_wait;
|
|
|
|
_pthread_detach;
|
|
|
|
_pthread_equal;
|
|
|
|
_pthread_exit;
|
|
|
|
_pthread_getspecific;
|
|
|
|
_pthread_join;
|
|
|
|
_pthread_key_create;
|
|
|
|
_pthread_key_delete;
|
|
|
|
_pthread_kill;
|
|
|
|
_pthread_main_np;
|
|
|
|
_pthread_mutex_destroy;
|
2007-11-27 16:22:21 +00:00
|
|
|
_pthread_mutex_init_calloc_cb;
|
2006-03-13 00:53:21 +00:00
|
|
|
_pthread_mutex_init;
|
|
|
|
_pthread_mutex_lock;
|
|
|
|
_pthread_mutex_trylock;
|
|
|
|
_pthread_mutex_unlock;
|
|
|
|
_pthread_mutexattr_destroy;
|
|
|
|
_pthread_mutexattr_init;
|
|
|
|
_pthread_mutexattr_settype;
|
|
|
|
_pthread_once;
|
|
|
|
_pthread_rwlock_destroy;
|
|
|
|
_pthread_rwlock_init;
|
|
|
|
_pthread_rwlock_rdlock;
|
|
|
|
_pthread_rwlock_tryrdlock;
|
|
|
|
_pthread_rwlock_trywrlock;
|
|
|
|
_pthread_rwlock_unlock;
|
|
|
|
_pthread_rwlock_wrlock;
|
|
|
|
_pthread_self;
|
|
|
|
_pthread_setcancelstate;
|
|
|
|
_pthread_setcanceltype;
|
|
|
|
_pthread_setspecific;
|
|
|
|
_pthread_sigmask;
|
|
|
|
_pthread_testcancel;
|
|
|
|
_spinlock;
|
|
|
|
_spinunlock;
|
2010-08-23 15:27:03 +00:00
|
|
|
_rtld_addr_phdr;
|
2008-11-27 11:27:59 +00:00
|
|
|
_rtld_atfork_pre;
|
|
|
|
_rtld_atfork_post;
|
2007-04-29 14:05:22 +00:00
|
|
|
_rtld_error; /* for private use */
|
2011-01-08 17:13:43 +00:00
|
|
|
_rtld_get_stack_prot;
|
2015-01-03 18:09:53 +00:00
|
|
|
_rtld_is_dlopened;
|
2007-04-29 14:05:22 +00:00
|
|
|
_rtld_thread_init; /* for private use */
|
2010-08-23 15:38:02 +00:00
|
|
|
__elf_phdr_match_addr;
|
2006-03-13 00:53:21 +00:00
|
|
|
_err;
|
|
|
|
_warn;
|
|
|
|
__fmtcheck;
|
2007-04-29 14:05:22 +00:00
|
|
|
/* __pw_match_entry; */
|
|
|
|
/* __pw_parse_entry; */
|
|
|
|
__fdnlist; /* used by libkvm */
|
|
|
|
/* __aout_fdnlist; */
|
|
|
|
/* __elf_is_okay__; */
|
|
|
|
/* __elf_fdnlist; */
|
2006-03-13 00:53:21 +00:00
|
|
|
__opendir2;
|
|
|
|
__pause;
|
|
|
|
_pause;
|
|
|
|
__raise;
|
|
|
|
_raise;
|
|
|
|
__sleep;
|
|
|
|
_sleep;
|
|
|
|
_rtld_allocate_tls;
|
|
|
|
_rtld_free_tls;
|
2007-04-29 14:05:22 +00:00
|
|
|
#if defined(i386)
|
|
|
|
___libc_tls_get_addr; /* x86 only */
|
|
|
|
#endif
|
|
|
|
__libc_tls_get_addr;
|
2006-03-13 00:53:21 +00:00
|
|
|
__tcdrain;
|
|
|
|
_tcdrain;
|
|
|
|
__usleep;
|
|
|
|
_usleep;
|
|
|
|
__wait;
|
|
|
|
_wait;
|
|
|
|
__waitpid;
|
|
|
|
_waitpid;
|
Use umtx to implement process sharable semaphore, to make this work,
now type sema_t is a structure which can be put in a shared memory area,
and multiple processes can operate it concurrently.
User can either use mmap(MAP_SHARED) + sem_init(pshared=1) or use sem_open()
to initialize a shared semaphore.
Named semaphore uses file system and is located in /tmp directory, and its
file name is prefixed with 'SEMD', so now it is chroot or jail friendly.
In simplist cases, both for named and un-named semaphore, userland code
does not have to enter kernel to reduce/increase semaphore's count.
The semaphore is designed to be crash-safe, it means even if an application
is crashed in the middle of operating semaphore, the semaphore state is
still safely recovered by later use, there is no waiter counter maintained
by userland code.
The main semaphore code is in libc and libthr only has some necessary stubs,
this makes it possible that a non-threaded application can use semaphore
without linking to thread library.
Old semaphore implementation is kept libc to maintain binary compatibility.
The kernel ksem API is no longer used in the new implemenation.
Discussed on: threads@
2010-01-05 02:37:59 +00:00
|
|
|
|
|
|
|
_libc_sem_init_compat;
|
|
|
|
_libc_sem_destroy_compat;
|
|
|
|
_libc_sem_open_compat;
|
|
|
|
_libc_sem_close_compat;
|
|
|
|
_libc_sem_unlink_compat;
|
|
|
|
_libc_sem_wait_compat;
|
|
|
|
_libc_sem_trywait_compat;
|
|
|
|
_libc_sem_timedwait_compat;
|
|
|
|
_libc_sem_post_compat;
|
|
|
|
_libc_sem_getvalue_compat;
|
2010-08-17 09:13:26 +00:00
|
|
|
|
2015-01-03 18:38:46 +00:00
|
|
|
__libc_tcdrain;
|
|
|
|
|
2010-08-17 09:13:26 +00:00
|
|
|
__elf_aux_vector;
|
2019-03-29 17:52:57 +00:00
|
|
|
__pthread_distribute_static_tls;
|
2011-01-08 17:13:43 +00:00
|
|
|
__pthread_map_stacks_exec;
|
2012-01-21 18:00:28 +00:00
|
|
|
__fillcontextx;
|
2013-05-28 04:54:16 +00:00
|
|
|
__fillcontextx2;
|
2012-01-21 18:00:28 +00:00
|
|
|
__getcontextx_size;
|
2006-03-13 00:53:21 +00:00
|
|
|
};
|