- 01 10月, 2012 1 次提交
-
-
由 Rich Felker 提交于
based on proposed patches by Daniel Cegiełka, with minor changes: - use a weak symbol for optreset so it doesn't clash with namespace - also reset optpos (position in multi-option arg like -lR) - also make getopt_long support reset
-
- 30 9月, 2012 2 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
also update syslog to use SOCK_CLOEXEC rather than separate fcntl step, to make it safe in multithreaded programs that run external programs. emulation is not atomic; it could be made atomic by holding a lock on forking during the operation, but this seems like overkill. my goal is not to achieve perfect behavior on old kernels (which have plenty of other imperfect behavior already) but to avoid catastrophic breakage in (1) syslog, which would give no output on old kernels with the change to use SOCK_CLOEXEC, and (2) programs built on a new kernel where configure scripts detected a working SOCK_CLOEXEC, which later get run on older kernels (they may otherwise fail to work completely).
-
- 26 9月, 2012 1 次提交
-
-
由 Rich Felker 提交于
also optimized a bit.
-
- 10 9月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 07 9月, 2012 3 次提交
-
-
由 Rich Felker 提交于
previously, it was pretty much random which one of these trees a given function appeared in. they have now been organized into: src/linux: non-POSIX linux syscalls (possibly shard with other nixen) src/legacy: various obsolete/legacy functions, mostly wrappers src/misc: still mostly uncategorized; some misc POSIX, some nonstd src/crypt: crypt hash functions further cleanup will be done later.
-
由 Rich Felker 提交于
void* does not implicitly convert to function pointer types.
-
由 Rich Felker 提交于
to deal with the fact that the public headers may be used with pre-c99 compilers, __restrict is used in place of restrict, and defined appropriately for any supported compiler. we also avoid the form [restrict] since older versions of gcc rejected it due to a bug in the original c99 standard, and instead use the form *restrict.
-
- 30 8月, 2012 4 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
all of the limits could use review, but err on the side of avoiding excessive rounds for now.
-
由 Rich Felker 提交于
these limits could definitely use review, but for now, i feel consistency and erring on the side of preventing servers from getting bogged down by excessively-slow user-provided settings (think .htpasswd) are the best policy. blowfish should be updated to match.
-
由 Rich Felker 提交于
based on versions sent to the list by nsz, with some simplification and debloating. i'd still like to get them a bit smaller, or ideally merge them into a single file with most of the code being shared, but that can be done later.
-
- 24 8月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 10 8月, 2012 2 次提交
-
-
由 Rich Felker 提交于
there are still some discussions going on about tweaking the code, but at least thing brings us to the point of having something working in the repository. hopefully the remaining major hashes (md5,sha) will follow soon.
-
由 Rich Felker 提交于
unfortunately, a large portion of programs which call crypt are not prepared for its failure and do not check that the return value is non-null before using it. thus, always "succeeding" but giving an unmatchable hash is reportedly a better behavior than failing on error. it was suggested that we could do this the same way as other implementations and put the null-to-unmatchable translation in the wrapper rather than the individual crypt modules like crypt_des, but when i tried to do it, i found it was making the logic in __crypt_r for keeping track of which hash type we're working with and whether it succeeded or failed much more complex, and potentially error-prone. the way i'm doing it now seems to have essentially zero cost, anyway.
-
- 03 8月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 29 6月, 2012 1 次提交
-
-
由 Rich Felker 提交于
the new version is largely the work of Solar Designer, with minor changes for integration with musl. compared to the old code, text size is reduced by about 7k, stack space usage by about 70k, and performance is greatly improved by avoiding expensive calculation of constant tables on each run. this version also adds support for extended des-based password hashes, which allow for unlimited key (password) length and configurable iteration counts. i've also published the interface for crypt_r in a new crypt.h header. especially since this is not a standard interface, i did not feel compelled to match the glibc abi for the crypt_data structure. the glibc structure is way too big to allocate on the stack; in fact it's so big that the first usage may cause the main thread to exceed its pre-committed stack size of 128k and thus could cause the program to crash even on systems with overcommit disabled. the only legitimate use of crypt_data for crypt_r is to store the hash string to return, so i've reserved 256 bytes, which should be more than sufficient (longest known password hashes are ~60 characters, and beyond that is possibly even exceeding some implementations' passwd file field size limit).
-
- 21 6月, 2012 1 次提交
-
-
由 Rich Felker 提交于
it should return the error code rather than 0/-1 and setting errno.
-
- 06 5月, 2012 1 次提交
-
-
由 Rich Felker 提交于
apparently some packages see stropts.h and want to be able to use this. the implementation checks that the file descriptor is valid by using fcntl/F_GETFD so it can report an error if not (as specified).
-
- 04 5月, 2012 1 次提交
-
-
由 Rich Felker 提交于
these actually work, but for now they prohibit actually setting priority levels and report min/max priority as 0.
-
- 25 4月, 2012 1 次提交
-
-
由 Rich Felker 提交于
i did some testing trying to switch malloc to use the new internal lock with priority inheritance, and my malloc contention test got 20-100 times slower. if priority inheritance futexes are this slow, it's simply too high a price to pay for avoiding priority inversion. maybe we can consider them somewhere down the road once the kernel folks get their act together on this (and perferably don't link it to glibc's inefficient lock API)... as such, i've switch __lock to use malloc's implementation of lightweight locks, and updated all the users of the code to use an array with a waiter count for their locks. this should give optimal performance in the vast majority of cases, and it's simple. malloc is still using its own internal copy of the lock code because it seems to yield measurably better performance with -O3 when it's inlined (20% or more difference in the contention stress test).
-
- 23 4月, 2012 1 次提交
-
-
由 Rich Felker 提交于
I actually wrote these a month ago but forgot to integrate them. ugly, probably-harmful-to-use functions, but some legacy apps want them...
-
- 22 4月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 17 4月, 2012 2 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
I'm not sure if it's legal for wordexp to modify this field, but this is the only easy/straightforward fix, and applications should not care. if it's an issue, i can work out a different (but more complex) solution later.
-
- 02 3月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 24 2月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 18 2月, 2012 2 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
- 25 1月, 2012 1 次提交
-
-
由 Rich Felker 提交于
based on patch by sh4rm4. these functions are deprecated; futimens and utimensat should be used instead in new programs.
-
- 21 1月, 2012 2 次提交
-
-
由 Rich Felker 提交于
this allows the full range of 64-bit limit arguments even on 32-bit systems. fallback to the old syscalls on old kernels that don't support prlimit.
-
由 Rich Felker 提交于
-
- 19 1月, 2012 1 次提交
-
-
由 Rich Felker 提交于
note that regardless of the name used, basename is always conformant. it never takes on the bogus gnu behavior, unlike glibc where basename is nonconformant when declared manually without including libgen.h.
-
- 16 9月, 2011 2 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
- 13 9月, 2011 1 次提交
-
-
由 Rich Felker 提交于
-
- 30 7月, 2011 1 次提交
-
-
由 Rich Felker 提交于
setrlimit is supposed to be per-process, not per-thread, but again linux gets it wrong. work around this in userspace. not only is it needed for correctness; setxid also depends on the resource limits for all threads being the same to avoid situations where temporarily unlimiting the limit succeeds in some threads but fails in others.
-
- 22 7月, 2011 2 次提交
-
-
由 Rich Felker 提交于
we cannot report failure after forking, so the idea is to ensure prior to fork that fd 0,1,2 exist. this will prevent dup2 from possibly hitting a resource limit and failing in the child process. fcntl rather than dup2 is used prior to forking to avoid race conditions.
-
由 Rich Felker 提交于
-1, not 0, indicates failure
-
- 26 6月, 2011 1 次提交
-
-
由 Rich Felker 提交于
previously, a potentially-indeterminate value from we_offs was being used, resulting in wrong we_wordc and subsequent crashes in the caller.
-